Hi, 

Hijacking this thread to ask if there any online resources available for x3 web calls that might help people like the OP. Content is really light at https://developer.sage.com/x3/ as it talks about file based import.

Good say,

Yes its described a bit in this section. The reason for the file import is because its easier to work with and the recommendation method of import. 

The use of published object windows is cumbersome and slow.

https://online-help.sageerpx3.com/erp/12/staticpost/import-export-soap-web-service/?highlight=SOAP

Hope that helps.

Wow, so the recommended method of integration is this file import process passing through clob data along to those AOWS subprograms?

When you say 'published object windows', your talking about publishing SIH object as a webservice and using that? As that's what I've done in the past.

That is correct, its fast, efficient and can be done in real-time or batch mode. The 'published object windows' are the published entry transactions of the objects. They are limited in that they only work for certain objects, they contain a lot of display fields which are not need for transaction generation, cluttering the XML (unless you unpublish them). You can use the AOWSIMPORT/AOWSEXPORT both via SOAP and internally to process transaction generation/export. 

That is correct, its fast, efficient and can be done in real-time or batch mode. The 'published object windows' are the published entry transactions of the objects. They are limited in that they only work for certain objects, they contain a lot of display fields which are not need for transaction generation, cluttering the XML (unless you unpublish them). You can use the AOWSIMPORT/AOWSEXPORT both via SOAP and internally to process transaction generation/export.