Analog to https://github.com/getodk/build/pull/284\
Likely start https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L51

I think this might be hard thing to fix, but figured I'd file it.

Given a form that uses the "or other" option, the logic that gets exported to XLSForm isn't correct.

• Untitled Form.odkbuild.zip
• Untitled-Form-export.xlsx

In the relevant column of favorite-color-other, I expect (selected(${question}, 'o')), but I get (selected(question, 'o')).

The Data Name should be wrapped with ${}. The path doesn't matter because pyxform requires that the Data Name to be unique.

likert widget https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L64

See https://forum.opendatakit.org/t/collect-error-problem-with-display-condition-for-node/14448 for more.

Add support for:

• #27
• #28
• #24
• #25
• #20

See getodk/build#278
Likely start: https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L197-L202

getodk/build#239 suggests to export the sanitised form title as form id, and the date hash as form version. If that PR were to be accepted, it would make most sense if build2xlsform were to copy this behaviour.

See getodk/build#320 (review)

ODK Build supports defaults, always and never for autosend/delete. This issue is a reminder to check whether exported XLSForms have the corresponding settings.

Tested version is: ODK Build 0.3.5 (offline version on Windows 64-bit OS)
Required text does not exported (i.e. there is no required_message column) in use the Export to XLSForm functionality in the File menu, even they are exists in the exported XML file when use the Export to XForm functionality.

This issue complements getodk/build#244
Merging #12 and #14 first would provide a clean starting point.

Guidance

XLSForm supports guidance as guidance_hint as per docs.

The following steps work and produce the attached file Short-guidance-export.xlsx

• Add guidance_hint to survey-fields https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L15
• Add guidance_hint to multilingual-fields https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L18
• Add guidance: \guidance_hint to https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L21

Short label

The XLSForm spec does not mention a short label anywhere.
Is a short label supported at all?
If it's not supported, then maybe issue a warning about information loss like at https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L238 ?

media label: image, big-image, audio, video https://github.com/getodk/build2xlsform/blob/master/src/convert.ls#L18

We probably need new logic to handle the label attribute form (not to be confused with form as in "XLSForm").

Analogous to getodk/build#165

I can't find anything about this in the ODK docs or in the XLSForm docs, but XLSForm/pyxform#178 reads like there should be columns "auto_send" and "auto_delete" with string values "true" or "false" next to the settings column "submission_url".

Likely entry point is gen-settings.

Note to self: issue/PR to docs re autosend/delete.

A numeric field with a slider will let a user type in the numeric min, max, and step width:

Note the values are numeric.

In the exported XForm, this becomes a <range ref="/data/group1/slider" start="0" end="8" step="1">. Note the values are quoted strings. The XForm however uploads and works fine.

In the exported XLSForm, this becomes a parameter with value start="0" end="8" step="1". Note the values are quoted strings - this is in contrast to the XLSForm spec showing numeric values for start, end, step. build2xlsform probably did nothing wrong(er) here. The XLSForm raises an error in ODK Central:

Manually changing the XLSForm parameter to start=0 end=8 step=1 fixes the ODK Central error.

How much of an issue is this for Build users? Question for user analytics: How many users go from Build to XLSForm (are we logging this?) and trip over sliders (are we logging form import warnings)?

Analog to getodk/build#284

This one is in the "hard" basket for sure. Audit settings in the XML are in the form metadata but need to become a question in the "survey" sheet of the XLSForm. The existing plumbing separates form metadata (like instance name - gen-settings) from form questions (convert-question). I don't see a way to add audit that doesn't change existing plumbing considerably.

Any ideas or pointers, @issa-tseng?

Steal this GH action