Browndog, you say the integration has a lot more functionality. Can you clarify this? Could there be some transformation logic which, when processed in batches of files could be triggering the duplication?

We haven't had any reports of order line duplications, and the O/E Order import is probably our most widely used import.

Do you have any other 3rd party add-ons enabled? We've seen instances where add-ons which subclass the Sage300 views can cause issues (which are more pronounced when things run in an automated fashion).

In terms of debugging, you may want to output each order to a CSV file, so you can see what the IMan dataset looked like; that way you can track whether it's a transform issue or something else.

Thanks for the reply, we are in the process of changing the web exports to support one order per file in the hope it will correct this issue, if not I will output a csv file per order and get back to you on this. We do you the 'Field Extender' add on from systronics, has this been known to cause any issues? I guess there is also no way the Sage 300 connector can access these fields? 

Field Extender - No known issues at present...sure we have a few customers out there with this running, and no we don't have the ability at present to target this add on.

In terms of your original issue...there shouldn't be any issue with multiple orders per file, unless you're doing something with the transform logic.

Thanks

Closed due to inactivity.