Thanks for the fantastic module, we are using it in a lot of projects!
When working on a new project, I encountered the following issue: When I am trying to embed a field that sets a @DEFAULT based on the value of another field into a descriptive field, the embedded field is always shown when the field from which the default is populated is filled in, even if branching logic should prevent it from showing.
I prepared a toy project (attached here). In this example, I would expect the "@DEFAULT (branching logic)" field not to show like is the case for the "no @DEFAULT (branching logic)" field.
It appears that the @DEFAULT supersedes the branching logic which I don't think should be the case. Is there anything I can do on my end or does the module code have to be modified? Thanks!
Defaultbranching_2022-02-22_1703.REDCap.xml.zip
Thanks for the fantastic module, we are using it in a lot of projects!
When working on a new project, I encountered the following issue: When I am trying to embed a field that sets a
@DEFAULTbased on the value of another field into a descriptive field, the embedded field is always shown when the field from which the default is populated is filled in, even if branching logic should prevent it from showing.I prepared a toy project (attached here). In this example, I would expect the "
@DEFAULT(branching logic)" field not to show like is the case for the "no@DEFAULT(branching logic)" field.It appears that the
@DEFAULTsupersedes the branching logic which I don't think should be the case. Is there anything I can do on my end or does the module code have to be modified? Thanks!Defaultbranching_2022-02-22_1703.REDCap.xml.zip