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.

RSS Google+TwitterLinkedInFacebookMVPQuixCC

No comments:

Post a Comment

Comments are moderated only for the purpose of keeping pesky spammers at bay.

SharePoint Remote Event Receivers are DEAD!!!

 Well, the time has finally come.  It was evident when Microsoft started pushing everyone to WebHooks, but this FAQ and related announcement...