How to Add Remit To Address ID to SmartConnect
Wednesday, December 11, 2013
David Youngquist, our support and eOne product guru, shares his tips on adding the Remit to Address ID to SmartConnect.
These steps will work for any eConnect parameter that is included in the eConnect SDK, but does not show up in SmartConnect.
1. First find out the Element Name that you need to add to SmartConnect. In this case we want to add the Remote to Address ID to the Payables Transaction Node. From the SDK, the correct format is this.
2. Open SmartConnect and go to the Maintenance tab. Click on Node Maintenance on the far right.
3. In the Node Maintenance Window, find the Node you need to add the parameter to and double click on it.
4. Scroll all the way to the bottom and click Add Field.
These steps will work for any eConnect parameter that is included in the eConnect SDK, but does not show up in SmartConnect.
1. First find out the Element Name that you need to add to SmartConnect. In this case we want to add the Remote to Address ID to the Payables Transaction Node. From the SDK, the correct format is this.
2. Open SmartConnect and go to the Maintenance tab. Click on Node Maintenance on the far right.
3. In the Node Maintenance Window, find the Node you need to add the parameter to and double click on it.
4. Scroll all the way to the bottom and click Add Field.
5. In the new line that gets added, type in the parameter name exactly like it shows in the eConnect documentation. Match the data type to what the eConnect SDK says. In this case it’s a string.
6. Click Save on the “Create / Update Node” window, then click Save on the “Microsoft Dynamics GP Node Maintenance” window.
7. Your map will now have the field available to map.
Has this article been helpful? Let us know which tech articles are your favorite! Leave a comment below.
Has this article been helpful? Let us know which tech articles are your favorite! Leave a comment below.
Hi, David,
Thanks for this article. I've followed these instructions, but SC doesn't seem to be saving my change.
Could there be a security setting somewhere that is preventing the save? Or is there something else that might be preventing this from being saved?
I have followed the instructions very precisely, and I've used the exact Element Name,
I have tried this as well and it does not work? Do you need the optional Node Builder add-on to be able to add standard eConnect fields such as the User Defined ones to pass values to a Post procedure?
Martin Jahn
FMT Consultants, LLC