In Dynamics GP, I’ve enabled the option for “Enable Long Description in Payables Transaction Entry”.
I’ve created a SmartConnect map for Dynamics GP Payables Transaction; however I don’t see the Long Description (LNGDESC) available in the mapping.
I adjusted the node in SmartConnect to add this field, so now I can map to it, and the integration runs. However, it does not get populated.
Why didn’t that work as I expected, and how do I populate that field in my integration?
If you’d like to watch a video explanation of this, see below or click here.
Updating Dynamics GP Payables Long Description
The purpose of the Node Maintenance is to be able to add your own Custom Nodes (ie stored procedures) to new or existing GP nodes in order to extend SmartConnect functionality.
The reason that adding the new field didn’t work is because of the fields and names that we see in Node Maintenance.
They correspond to the parameters of the same name in MS SQL for that stored procedure – taPMTransactionInsert in this case.
Adding the LNGDESC to SmartConnect Node Maintenance for the “Create payables transaction” works and shows to be mapped in the SmartConnect UI. Since there isn’t actually a parameter for @I_vLNGDESC on the Microsoft eConnect proc (or code in the proc to do it), the data isn’t sent to the proc and therefore the PM10000.LNGDESC doesn’t get written.
To resolve this, we could use the developer taPMTransactionInsertPost proc and add the business logic to that stored procedure to update the LNGDESC field, as proposed in this KB for a similar issue with Account User Defined fields.
However, the easier and recommended solution is to create an “after document success” SQL Task in SmartConnect and update the data directly in the table.
I’m using a GP Rolling Column to get my “Next” voucher number. Make sure to mark the checkbox for “Use for Global Variable,” as noted in the screenshot below.
If I were assigning the voucher number from the source data, we could skip this step. However, most users will use a GP Rolling Column to get that “next number”.
use GlobalCompanyID update dbo.PM10000 set LNGDESC = '_LongDesc' where VCHNUMWK = 'GlobalRollingColumn'
Now that the GP Rolling Column is marked, we can create a new “After Document Succeeds” SQL Task.
Using the code above, this will update the PM10000.LNGDESC to my data field is. The value GlobalRollingColumn will be replaced with the Voucher Number that is being used on the document.
The GlobalCompanyID will be replaced with the correct target database — TWO24 in my case, since that is my only company in this GP install.
After adding the new SQL task and re-running the integration, we can see that the SQL Task was successful and the Long Description is now populated.
You can download the SmartConnect 21.1.0.1682 map used in this article in the link below.
Please reach out to support@eonesolutions.com with any questions on updating Dynamics GP Payables Long Description with SmartConnect.
