Unfortunately, ODK is inconsistent with the form file name, the form id, and the form title.
ODK Collect stores forms by their form title. ODK Aggregates and also the XForms XML itself calls a form_id by the form_id specified in your XLS settings tag. But, JavaRosa's FormDef which supplies a form id is an integer value.
That form id is what gets to OMK Android via intents, but this number isn't very useful, because it isn't the form ID we know and love.
So, for now, we're just going to have to name our constraint JSON file by the form title. That's the file name used on the file system in ODK Collect. It doesn't really matter, but it's an inconsistency.
This change will require modification in JavaRosa and ODK Collect.
Encountered during implementation of #147 and #148 via constraints sprint #117.
Unfortunately, ODK is inconsistent with the form file name, the form id, and the form title.
ODK Collect stores forms by their form title. ODK Aggregates and also the XForms XML itself calls a
form_id
by theform_id
specified in your XLS settings tag. But, JavaRosa'sFormDef
which supplies a form id is an integer value.That form id is what gets to OMK Android via intents, but this number isn't very useful, because it isn't the form ID we know and love.
So, for now, we're just going to have to name our constraint JSON file by the form title. That's the file name used on the file system in ODK Collect. It doesn't really matter, but it's an inconsistency.
This change will require modification in JavaRosa and ODK Collect.
Encountered during implementation of #147 and #148 via constraints sprint #117.