Sage 300 Purchase Order Mapping Error (4 replies)
Too add to this a prexisitng integration since V3 which fortunately still works is also showing bizarre mapping, the field says 'Allocate from Serial' but is actually mapped to VDCODE
Browndog, what happens if you try to unmap and then remap the 'Field5' field?
If I ummap the field from the working integration and reinstate it then it becomes 'TAXAMOUNT4' the same as the new integration
We determined this was an issue with the Sage300 installation, after logging onto the client's IMan server.
Sage300 was returning the incorrect field description for the field e.g. The TAXAMOUNT4 field was returning 'Vendor'...leading the customer to select the incorrect field name (see field mapping screenshot below).
We created a macro (see text) to print each field name and description for the Purchase Order Header view (PO0620).
Throughout the file generated we could see numerous incorrect descriptions.
I am creating an integration which is creating a new purchase order, when I go to setup the mapping in the Sage 300 connector no matter what i do 'TAXAMOUNT4' is always mapped and creates a tax related error if the integration is run. There seems no way to stop the Tax amount field getting mapped.
I have installed the latest release v4.1 update 2 to see if it remedied the issue but still it occurs. This does seem like a connector bug and is apparent on both our production server and development server.
Windows Server 2008 R2 Sage 2014