iMan rejecting valid stock records (3 replies)
I suspect this is due to capitalisation of the item code.
The internal lookup which is performed is case sensitive.
The codes are forced UPPER in both data sets as mentioned above, the sister database was formed on the back of the parent DB so each record is nigh identical, how do we combat the lookup in this scenario as case validation isn't necessarily needed.
But you have a column LookupValidItem which is failing.
There must be a reason....you will need to provide a screenshot of the formula in this field.
Hi,
We've been using this a while now to move about inter company transactions between Sage200 > Sage200
iMan isn't happy with some stock records.
The records exist in both systems with carbon copy settings that match every other stock item, with the exception of the item id field between the data sets.
I have been confused now as to why some stock codes are fine, and some are invalid?
Is there a better script formula to evaluate exactly why iMan won't processed the object?