question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

action order on same field

See original GitHub issue

Hello, I am confused by following in docs:

For the above, given that there are conflicting commands, the more conservative is given preference. For example: REMOVE > BLANK > REPLACE > JITTER/KEEP/ADD … If I specify to blank a header and remove it, it will be removed If I specify to replace a header and blank it, it will be blanked

Also

Most of the time, you won’t need to specify remove, because it is the default

But at the same time there is an example of

ADD PatientIdentityRemoved Yes
REMOVE ALL
KEEP PixelData

Here I naturally make assumption that ALL means ALL, so each field is removed, and according to rules quoted above, REMOVE rules over KEEP, so tag kinda has to be removed. How does it work? How is PixelData expected to be kept?

In my usecase I want to drop all information except for certain tags, part of them I want to keep, part of them I want to replace with my custom func. I don’t want to manage full set of DICOM tags, but rather remove all and preserve only certain subset. How?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:23 (23 by maintainers)

github_iconTop GitHub Comments

1reaction
vsochcommented, Dec 12, 2021

Haha definitely! It’s probably not the best example - they always used colored balls in bags as examples in statistics courses, so I’m not sure I did it justice 😆

0reactions
vsochcommented, Dec 20, 2021

Closed with #198

Read more comments on GitHub >

github_iconTop Results From Across the Web

What order will actions trigger in? | Discussions
I have two actions. Both trigger off the same thing: a record being created with a specific field not being blank. The first...
Read more >
Order of Execution of WF Rules and Process Builder on the ...
According to order of execution, if we update a field via workflow and if before/after trigger exists, then trigger will fire on that...
Read more >
sort field in action monitor - SAP Community
Hi,. You can use the sort fields to process a series of actions in a defined order during batch processing. For this, you...
Read more >
Considerations for Field Update Actions - Salesforce Help
Field updates occur after case assignment, lead assignment, and auto-response rules. Field updates function independently of field-level security. Therefore, a ...
Read more >
Fields Parameter Tip 2 - Fix Category Sort Order - YouTube
More Information below Another tip when working with the new Field Parameter - How to set the sort order of a chosen...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found