Instead of breaking your brain trying to figure out how to number these nodes, simply leave the value as 0 (Zero) to force eConnect to auto number it going into Great Plains.
LaterC
18 August 2006
eConnect SOPTransaction.xsd LNITMSEQ node
OK, so this one is in the help documentation if you dig deep enough, but it puzzled me for a while. The problem is the weird way Great Plains number with this node in multiples of 16384.
Instead of breaking your brain trying to figure out how to number these nodes, simply leave the value as 0 (Zero) to force eConnect to auto number it going into Great Plains.
LaterC
Instead of breaking your brain trying to figure out how to number these nodes, simply leave the value as 0 (Zero) to force eConnect to auto number it going into Great Plains.
LaterC
Subscribe to:
Post Comments (Atom)
-
Ever wondered what the new SharePoint Online URLs are all about? Take for example https://cjvandyk.sharepoint.us/:x:/r/sites/Site1... What ...
-
When using NuGet, we can easily run into assembly reference issues. A notorious error message is: CS0012: The type ‘System.Object’ is def...
-
Every so often, you run across the need to redirect a page somewhere else, like after a server migration when DNS isn’t used. By simply addi...
No comments:
Post a Comment
Comments are moderated only for the purpose of keeping pesky spammers at bay.