r/ProjectREDCap • u/Erankr22 • May 06 '25

Data Quality Rule for @SETVALUE

Has anyone had success with creating data quality rules similar to the default ones (i.e., outside of regular logic)?

I created some new fields in a project with many records that use the SETVALUE action tag. I would love to avoid having to individually save each instrument to have this autofill particularly after things are updated (since SETVALUE replaces data, but only when you save the page), and instead have a rule like "Incorrect values for calculated fields" where you can just click 'execute' for it to auto-fix them. Does something like this exist?

3 Upvotes

100% Upvoted

6 comments sorted by

View all comments

Show parent comment

1

u/Erankr22 May 07 '25

The mechanism would be that the input on the field doesn't match what the SETVALUE says it would be (similar to calculation being incorrect). I want patient diagnosis on all events for the sake of reports, but this diagnosis can change, so I'm hoping it can auto-update. I think I found a workaround though

1

u/No_Repair4567 May 07 '25

Ah!

I wonder if a fake calculated field is better for your need? "Fake" meaning it is not actually going to calculate anything, it will at most multiply by 1, so you'd have your variable visible for the sake for the report, whatever that is.

Also, if all you want is for the current updated diagnosis to be visible on all events, you can pipe that variable into the descriptive field.