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







