Skip to content

Add @SETVALUE behavior #5

Description

@pbchase

Brandon Potvin asked on (2026-08-18 11:40)

Is it possible to have this work more like @setvalue instead of @DEFAULTwhere it will evaluate the condition each visit to the record? I have one use case where I would like to populate the username from the redcap_user_information table based on the email address. This works as a Dynamic SQL field, but of course I have to select it from the dropdown.

I proposed adding an action tag @SETVALUE-FROM-QUERY= 'query_name' much like we currently support @DEFAULT-FROM-QUERY= 'query_name'. I also proposed adding a project-level configuration option to enable the @SETVALUE-FROM-QUERY behavior where needed. That would prevent any performance impact for projects that don't need this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions