What settings validate unique orders?

[mrlinton]

We are loading O/E orders through the sdk for 5.6 and on some systems we test on we can load orders without ORDNUMBER populated but on some, we have to populate it with a unique value. On the problem systems, we receive 'Order. Record already exists.' when the order doesn't have ORDNUMBER populated and we expected it to auto increment with the next order number. Populating '*** NEW ***' also does not change the behavior.

Are there certain settings (or modules) within Accpac that would affect this? Again, we can take the exact same order and load successfully on other deployments of Accpac 5.6. Attached is the test file.

Any ideas to try out would be greatly appreciated. Thank you.

 

[Jay Converse]

Never set the ORDNUMBER, let the system do it.

 

[mrlinton]

Yes, exactly, that is what we want to do but in this one scenario that wasn't working so we were wondering if there is anything else that dictates when this would work.

We were able to get past the problem by putting Accpac to a clean install state but that still doesn't give us the root of the issue so if others have ideas, we'd still like to know. Thank you.

 

[Jay Converse]

Take ORDNUMBER (and 90% of the other fields) out of that file.