Hi Karl,
Thanks for using Dynamics Communities and that’s a great question.
First, Karl you are 100% correct that the taRMTransaction eConnect Node does not allow you to map the GLPOSTDT field.
While I can’t provide you with the Developers insight as to ‘why’ that field was not included as mappable in this node, I can tell you that instead of relying on dexterity code or any front-end functionality of the Microsoft Dynamics GP product, eConnect inserts/updates data directly in appropriate tables using the eConnect stored procedures.
There is business logic built into eConnect, but it is not exactly the same as updating a transaction on the front end. As such, there are some areas on eConnect that behave differently, and this is one of those areas (as you’ve already found).
I looked at the taRMTransaction stored procedure, and currently the GLPOSTDT field gets updated to match the @I_vDOCDATE (the document date you pass in/map).
Now, on to ‘how’ you may be able to get the results you’re looking for:
I think you should be able to use the taRMTransactionPost procedure to add some custom logic to update the GLPOSTDT in the RM10301 as desired.
There are five mappable user defined fields in the taRMTransaction procedure, one of which you could use to map the GLPOSTDT. These are all character data types, so you’d have to map it as a character originally and convert it to a date format in the post procedure:
@I_vUSRDEFND1 char(50),
@I_vUSRDEFND2 char(50),
@I_vUSRDEFND3 char(50),
@I_vUSRDEFND4 varchar(8000),
@I_vUSRDEFND5 varchar(8000),
The logic you use in the taRMTransactionPost procedure may look something like this (assuming the first user defined field is where the GLPOSTDT is mapped):
/* Create Custom Business Logic */
UPDATE RM10301 SET GLPOSTDT = CONVERT(DATETIME, @I_vUSRDEFND1) WHERE DOCNUMBR = @I_vDOCNUMBR AND CUSTNMBR = @I_vCUSTNMBR
/* End Create Custom Business Logic */
I hope this helps!
Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP
