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
This is very similar to the issue described in #520, where the xml generated is not using the action but rather something else in the wsdl definition. Here is a link to the full wsdl document I'm using. It's a bit sensitive to case--only likes the :lower_camelcase formatted output, and I have to quote some fields such as 'objectID' and 'XCoord'. Unfortunately the endpoint is secured and there is no public version for testing. A few of the actions that get mangled include :write_case_eform_data and :retrieve_code_book.
Here's an example of a wsdl definition (it's broken down into many pieces):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is very similar to the issue described in #520, where the xml generated is not using the action but rather something else in the wsdl definition. Here is a link to the full wsdl document I'm using. It's a bit sensitive to case--only likes the :lower_camelcase formatted output, and I have to quote some fields such as 'objectID' and 'XCoord'. Unfortunately the endpoint is secured and there is no public version for testing. A few of the actions that get mangled include :write_case_eform_data and :retrieve_code_book.
Here's an example of a wsdl definition (it's broken down into many pieces):
It should (and used to in earlier versions) produce output that looks like this:
But with the latest release (2.4) it now produces this, generating errors similar to those described in #520:
Note specifically that it's sending "flt:FLEformFields" as the tag instead of "writeCaseEformData".
The text was updated successfully, but these errors were encountered: