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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: