Integration Manager - Vendor

(0) Share

Report

Posted on by Community Member Microsoft Employee

Not all fields import when using the eConnect Destination...

When using Microsoft Dynamics GP eConnect > Purchasing > Vendor as the Destination, the import does not bring over ZIP Code, Phone 1, or Phone 2. However, using the exact same data source and mappings, these fields DO populate when using the plain ol' Microsoft Dynamics GP > Payables Management > Vendor as the Destination. Is this a bug? Can anyone else import these fields using the eConnect destination? Ideally we want to use the eConnect version since we will be "automating" this import...

My versions;

GP 11.00.2248

IM 11.00.2055

*This post is locked for comments

All responses (12)

Answers (1)

Maria Carrero 150 on at

Like (0)

Report

RE: Integration Manager - Vendor

Hi Mark,

What do you refer?

If you need documentation, you can find the manuals in the folder Help\Documentation. About add the code, go to Properties Integration, tab Scripts and select after document, click on Open Button and paste the code there, you need to change the Source Fields Name according to your file (<Source Name>.<Column name>).

Mary
Community Member Microsoft Employee on at

Like (0)

Report

RE: Integration Manager - Vendor

Maria

Do you have any information on how you wrote your integration?

I am trying to provide a way for our AP team to update existing vendors as well as add new ones.

Thank you

mark
Maria Carrero 150 on at

Like (0)

Report

RE: Integration Manager - Vendor

I am working with only one source query.

I ran profiler, I could to see some parameters values are not sending correctly to the stored procedures eConnect by IM. However, some fields are sending for example, vendor contact name is sending to stored procedure of Master vendor, but it is not sending to store procedure of address vendor.
Mariano Gomez 26,225 on at

Like (0)

Report

RE: Integration Manager - Vendor

While Jonathan points this to a bug, I am not too convinced. When you look at the eConnect XML schemas, in order to import the vendor information, you must first import the address then the vendor information second. This leads me to believe you are working with only one source query.

If you look at the vendor destination, it requires two source queries: one for the vendor collection and one for the address collection. How many source queries are you working with?
Jeff Bloch 95 on at

Like (0)

Report

RE: Integration Manager - Vendor

Thanks for the script. There is one minor tweak that I had to make on the script and then it worked:

sSQL = sSQL & " PHNUMBR1 = '" & SourceFields("Vendor.phone1") & "'"

Changed to (added , before PHNUMBR1)

sSQL = sSQL & " ,PHNUMBR1 = '" & SourceFields("Vendor.phone1") & "'"

Jeff
Community Member Microsoft Employee on at

Like (0)

Report

RE: Integration Manager - Vendor

Jonathan,

Can you check if this is also a bug ?

community.dynamics.com/.../114995.aspx

e Connect programmers reference guide show Print_Phone_NumberGB is a member of taSopLineIvcInsert_ItemsTaSopLineIvcInsert Class class.

How ever the e Connect objects say is not

Sorry linked to a different thread just to reach you!

Thanks!

Sanjay
Jonathan Fear on at

Like (0)

Report

RE: Integration Manager - Vendor

This is a bug that we are looking into. The script Maria noted should be a good workaround (I haven't tested just reviewed it).
Verified answer

Maria Carrero 150 on at

Like (0)

Report

RE: Integration Manager - Vendor

Hi,

I fixed the issue!!! :) , adding script after document. This is the script:

'Create a new connection object

Set MyCon = CreateObject("ADODB.Connection")

'Open the connection to the database

MyCon.ConnectionString = "database=" & GPConnection.GPConnInterCompanyID

GPConnection.Open(MyCon)

'Build a string containing your SQL Select Statement

sSQL = "UPDATE PM00200 SET "

sSQL = sSQL & " VNDCNTCT = '" & SourceFields("Vendor.ContactName") & "'"

sSQL = sSQL & " ,PHNUMBR1 = '" & SourceFields("Vendor.phone1") & "'"

sSQL = sSQL & " ,PHNUMBR2 = '" & SourceFields("Vendor.phone2") & "'"

sSQL = sSQL & " ,ZIPCODE = '" & SourceFields("Vendor.ZIP_code") & "'"

sSQL = sSQL & " WHERE VENDORID = '" & SourceFields("Vendor.Vendor ID") & "'"

sSQL = sSQL & " UPDATE PM00300 SET "

sSQL = sSQL & " PHNUMBR1 = '" & SourceFields("Vendor.phone1") & "'"

sSQL = sSQL & " ,PHNUMBR2 = '" & SourceFields("Vendor.phone2") & "'"

sSQL = sSQL & " ,ZIPCODE = '" & SourceFields("Vendor.ZIP_code") & "'"

sSQL = sSQL & " WHERE VENDORID = '" & SourceFields("Vendor.Vendor ID") & "' AND ADRSCODE = 'PRIMARY'"

MyCon.Execute(sSQL)

'Close the connection

Call MyCon.Close

'Release the object

Set MyCon = nothing
Suggested answer

Community Member Microsoft Employee on at

Like (0)

Report

RE: Integration Manager - Vendor

updated the direct e Connect example to update contact name @ www.sanjaykumar.us/.../e-connect-example-create-vendor-multiple-addresses

Cheers!

Sanjay
Harold Worby 1,325 on at

Like (0)

Report

RE: Integration Manager - Vendor

had the same problem in GP2010, Needed to use the Standard GP connection