Integration Manager - Vendor

(0) Share

Report

Posted on by Community Member

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

I have the same question (0)

All responses (12)

Answers (1)

Suggested answer

Community Member on at

Like (0)

Report

Hi AB,

Tested your findings at GP 12.00.1482 (SP2) / IM 12.00.1488, vendor master integration with e Connect destination, the result is same. Phone numbers 1 - 2 - 3 and Zip code does not get updated.

Tested the vendor creation directly using e Connect directly / without using integration manager, phone numbers and zip codes do get updated.

As you are planning for automating the imports using e Connect you should be fine.

Find test results and source code for e Connect vendor integration @ www.sanjaykumar.us/.../e-connect-example-create-vendor-multiple-addresses .

Cheers!

Sanjay

Was this reply helpful? Yes No
Maria Carrero 150 on at

Like (0)

Report

Hi AB,

I using Integration Manager too with vendor integration, tested with phone 1 and zip code and these does not updated.

My additional problem is the contact name field, in this case, the value is updated in address table, but it is does not get updated in the master vendor table.

Did you find any solution for that in your case?

My versions:

GP 12.00.1384

IM 12.00.1488

Was this reply helpful? Yes No
Harold Worby 1,331 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

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

Cheers!

Sanjay

Was this reply helpful? Yes No
Verified answer

Maria Carrero 150 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

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).

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

Was this reply helpful? Yes No
Jeff Bloch 95 on at

Like (0)

Report

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

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Maria Carrero 150 on at

Like (0)

Report

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.

Was this reply helpful? Yes No