You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.
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)?
The text was updated successfully, but these errors were encountered:
A numeric field with a slider will let a user type in the numeric min, max, and step width:
![image](https://user-images.githubusercontent.com/762815/145322063-5261f9c9-578b-41c4-b2ba-67c7f2e9dc65.png)
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
![image](https://user-images.githubusercontent.com/762815/145322037-38e94526-1688-4dfc-bbbf-0ec94b4fe62e.png)
parameter
with valuestart="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)?
The text was updated successfully, but these errors were encountered: