Title: Dynamic Data Attachments / lookup / pulldata / itemsets.csv not populating Child form despite exhaustive setup
Hello KoboToolbox Community Team,
I’m posting here after extensive troubleshooting to seek technical guidance on a persistent issue with linking two Kobo forms.
- End goal
We need to link two Kobo forms such that:
1.1 A Parent form collects master data (Unique_ID, Name_of_the_child, Age).
1.2 A Child form dynamically pulls and auto-populates this data at runtime when the same Unique_ID is entered.
1.3 The linkage must be fully dynamic:
• No CSV or media uploads
• No manual file refresh or replacement
• No technical steps required from field staff
In short: live Parent → Child form linking with automatic population using Kobo-supported functionality.
2. Approaches we have already tried (in detail)
2.1 Dynamic Data Attachments (primary and preferred approach)
2.1.1 Parent form configuration:
• Data sharing enabled
• Fields explicitly selected for sharing (Unique_ID, Name_of_the_child, Age)
• Verified submissions exist and are visible in the Parent form Data tab
2.1.2 Child form configuration:
• Parent imported via Settings → Connect Projects
• Import alias consistently used (e.g., parent_test_form)
• Import refreshed after field selection
• Child form redeployed after every change
2.1.3 XLSForm logic used in Child:
• lookup() functions, for example:
lookup(‘parent_test_form’,‘Name_of_the_child’,‘Unique_ID’, ${Unique_ID})
lookup(‘parent_test_form’,‘Age’,‘Unique_ID’, ${Unique_ID})
• Values stored in calculate fields and displayed via read-only text/integer fields
2.1.4 Result:
• Child form loads without validation errors
• lookup() values remain blank, as if the imported dataset contains zero rows
2.2 CSV + pulldata() approaches (legacy testing)
2.2.1 Exported parent data using CSV and CSV (legacy)
2.2.2 Tested pulldata(), instance(), and xml-external approaches
2.2.3 Uploaded CSV files via Media and synced devices
2.2.4 Result:
• Inconsistent behavior across deployments
• Errors such as “Failed to load parent.csv”
• Requires manual CSV updates whenever parent data changes, which is operationally not viable
2.3 itemsets.csv approach
2.3.1 Generated itemsets.csv from parent data to populate select_one / select_multiple fields
2.3.2 Configured choices sheet to reference itemsets.csv
2.3.3 Uploaded itemsets.csv via Media and redeployed forms
2.3.4 Result:
• Data only updates when itemsets.csv is manually regenerated and reuploaded
• Not dynamic and unsuitable for workflows where parent data changes frequently
• Requires technically skilled intervention, which field staff cannot reliably perform
2.4 Rebuilds and validation checks
2.4.1 Rebuilt both Parent and Child forms from scratch multiple times
2.4.2 Confirmed:
• Exact field-name matches
• Matching data types (text vs integer)
• No duplicate Unique_ID values
• Parent and Child are on the same Kobo server
2.4.3 Tested on:
• Web forms
• KoboCollect after sync
The issue persists across all rebuilds.
3. Observed problem pattern
3.1 Parent data is valid and visible in the Parent form Data tab
3.2 Parent dataset is selectable and importable in the Child form
3.3 Field selection for sharing is confirmed
3.4 Despite this, the Child form behaves as if the imported dataset is empty:
• lookup() returns blank values
• No visible runtime or validation errors
3.5 There are no exposed diagnostics indicating:
• Whether the shared dataset is being generated correctly
• Whether rows exist in the imported dataset
• Whether lookup execution is failing silently
4. What we are seeking help with
4.1 Whether this behavior points to a known issue or limitation with Dynamic Data Attachments
4.2 Whether there are backend logs, dataset status indicators, or debugging tools to verify dataset generation, row counts, or lookup execution
4.3 Any minimal reproducible example or recommended configuration known to work reliably for Parent → Child auto-population without CSV or itemsets.csv uploads
This functionality is mission-critical for our workflow, as it significantly reduces administrative load and field-level errors.
We are happy to share sanitized XLSForms or screenshots if required.
Thank you for your time and support.
Best regards,
Mohammed Saad.
