REDCap troubleshooting

REDCap branching logic not working? Check the field name and stored code.

A branching rule can look reasonable in the Online Designer while comparing a value the field never stores. Labels are written for people; branching logic reads the underlying codes in the project definition.

FormPath reads an exported REDCap Data Dictionary CSV and translates the supported logic into a finite model. It can produce evidence about that translated model, while clearly separating conditions that still need to be tested inside REDCap.

Diagnostic checklist

Work from the stored answer outward.

  1. 01

    Confirm every referenced field name

    Search the exported dictionary for each name in square brackets. A renamed, deleted, or mistyped source field cannot supply the answer the branch expects.

  2. 02

    Compare codes, not display labels

    A radio field may display “Residential” while storing “1.” The branching expression must compare the stored code.

  3. 03

    Check checkbox references carefully

    REDCap checkbox conditions name both a field and a choice code, such as [services(2)] = '1'. A stale code inside the parentheses points at the wrong option.

  4. 04

    Set runtime-dependent logic aside

    Smart variables, events, repeating instances, datediff(), and server-dependent functions require the live REDCap project. FormPath lists the unsupported dependencies it detects; project and runtime behavior outside the stated scope still requires live testing.

Example

A label used where REDCap expects a code

Both dictionaries display the same label. Only the second branch compares the code supplied by the radio field. FormPath can inspect this finite translated condition; the corrected behavior should still be confirmed in REDCap.

Branch that compares display text
field_name,field_type,select_choices_or_calculations,branching_logic
property_use,radio,"1, Residential | 2, Investment",
mortgage_status,text,,"[property_use] = 'Residential'"
Branch that compares the stored code
field_name,field_type,select_choices_or_calculations,branching_logic
property_use,radio,"1, Residential | 2, Investment",
mortgage_status,text,,"[property_use] = '1'"

Honest boundary

What this guide and analyzer do not establish.

  • FormPath translates a supported subset of a Data Dictionary CSV; it does not run inside REDCap or validate an entire project.
  • Events, repeating instruments, smart variables, datediff(), and other runtime or server behavior require native REDCap testing.
  • A clean result applies only to the completed translated scope shown in the report and is not a claim about live records, alerts, queues, or survey behavior.

No signup · no upload

Ask which supported answer states are actually possible.

FormPath runs locally and exports each finding, how it was checked, and any important limits as JSON or Markdown.

Check a REDCap dictionary