Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zeep SOAP client: No element 'DocumentElement' in namespace None. Available elements are: NewDataSet #240

Closed
jurrian opened this issue Sep 11, 2019 · 1 comment
Assignees
Labels
bug High priority issue for (blocking) problems
Milestone

Comments

@jurrian
Copy link
Contributor

jurrian commented Sep 11, 2019

Replacing suds SOAP client by zeep caused the following exception for all usage of the GetListReport operation: No element 'DocumentElement' in namespace None. Available elements are: NewDataSet.

After some extensive investigation it turns out that not the Zeep package is doing it wrong but the data supplier iBabs is malformed. It turns out that there is a mismatch between the NewDataSet which is defined in the scheme and DocumentElement which is listed in the data itself. I have contacted iBabs and suggested to replace NewDataSet by the latter to resolve the issue. As far as I know GetListReport is the only operation that includes a XML Schema.

Further, since there is currently no obvious way around malformed data, I've created an issue to request a setting to ignore the supplied XML schema. For an example of the malformed data see:
mvantellingen/python-zeep#1004

@jurrian jurrian added the bug High priority issue for (blocking) problems label Sep 11, 2019
@jurrian jurrian self-assigned this Sep 11, 2019
@jurrian
Copy link
Contributor Author

jurrian commented Sep 17, 2019

iBabs has been working on a new method called GetListReportDataSet that will have the right XML Schema, with an DocumentElement. This issue will be closed when that comes to production.

@jurrian jurrian added this to the V1.3.4 milestone Sep 20, 2019
jurrian pushed a commit that referenced this issue Sep 20, 2019
This new iBabs method fixed an invalid XML schema
@jurrian jurrian closed this as completed Sep 20, 2019
jurrian pushed a commit that referenced this issue Sep 20, 2019
This new iBabs method fixed an invalid XML schema
jurrian pushed a commit that referenced this issue Sep 20, 2019
This new iBabs method fixed an invalid XML schema
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug High priority issue for (blocking) problems
Projects
None yet
Development

No branches or pull requests

1 participant