Hello, guys
When creating a form in ODK Central, it is possible to set a formId (internally known as xmlFormId) that contains spaces or other URL-unsafe characters — for example, anything AA.
This creates a problem when calling the API, because the formId must then be percent-encoded in the URL (e.g., anything%20AA). This is an unexpected and error-prone pattern for API consumers.
Currently, I interact almost entirely with ODK through its API, and forms created this way would break all of my API calls that use the formId, as I understand that an identifier property should not allow characters of this nature.
Is there any explanation for why these characters are allowed? Is there any plan to improve this behavior in the future?