Skip to content
This repository has been archived by the owner on Nov 2, 2023. It is now read-only.

Better document the differences with ${xlsform} style interpolation #212

Open
drinckes opened this issue Jan 10, 2019 · 3 comments
Open
Milestone

Comments

@drinckes
Copy link

When building a form using the spreadsheet/XLSForm approach, you reference other fields with ${field_name}, e.g.:

not(boolean(${gps_location})) or number(${gps_location})>15

But when specifying them in the online builder, I have to reference them with /data/field_name, e.g.:

not(boolean(/data/gps_location)) or number(/data/gps_location)>15

Is this correct? I couldn't find this in the documentation - did I just miss it?

@issa-tseng
Copy link
Member

yeah, that's correct. xlsform sort of invents its own syntax to try to make things easier. when odk build was created (ten years ago!) i was shy about doing that sort of thing and just stuck as close to actual xforms as possible.

the documentation doesn't really talk about this much because.. it sort of used to just be the normal way of doing things! i don't think anybody really anticipated that xlsform might be so successful that people would learn it first and then have to switch to xforms to do stuff.

@drinckes
Copy link
Author

drinckes commented Jan 11, 2019

Thanks Issa, the documentation refers to accessing variables using the xlsform syntax, so it was really hard to work out what I had to do in the online editor. Any thoughts about where a note would be useful - in that doc or in the help for the online builder?

@issa-tseng
Copy link
Member

oh wow, i see. probably both?

@issa-tseng issa-tseng changed the title Field references different Better document the differences with ${xlsform} style interpolation Mar 6, 2019
@florianm florianm added this to the 0.5.0 milestone Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants