When using MS Dynamics AX WebServices, we could get errors that indicated that the fields in the WebService call was not send in the correct order. The AX WebServices needs the fields in the XML message to be written in a specific order.
The problem could be fixed temporarely by doing a ReadDesign on the AX WS Connection.
This is fixed as the ReadDesign now generates a sequential Consecutive Number and stores this with the design. In this way the layout are read from the configuration database in the same order as written and we can ensure that the XML messages are generated correctly.
For MS Dynamics AX WS, you can just upgrade the corresponding RapidiConnector.
This problem can also happen with E-conomic and in this case you have to upgrade the central service.
version 3.2.88h (January 2014)
About the author
Michael Bock
Michael founded Rapidi on technological excellence, fantastic customer service and continuous improvement. A data integration specialist since 1987, he remains focused on creating technology that solves real business problems.
