web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Internet Fields Population Integration Manager

(0) ShareShare
ReportReport
Posted on by

Hi all, migrating to GP2013 from GP10 I understand there is now internet information that needs populating in Customer Cards for electronic invoicing. Specifically the email addresses in the To... and Cc... fields.

The problem is I see now way of mass populating these using Integration Manager. Has someone found a way around this rather than manually going through every customer card manually populating? I see it's SY01200 table that holds the data.

Thanks.

*This post is locked for comments

I have the same question (0)
  • Richard Wheeler Profile Picture
    75,848 Moderator on at

    Internet information is tied to the customer address card. If you create an insert/update integration and then when you are mapping choose Internet Information under Addresses. You may need to change to Record Source under Options but it should allow you to update the internet information per customer address provided your input file has the current customer and address ID's.

  • Community Member Profile Picture
    on at

    Thanks, perhaps it's just me but I see no To... or Cc... fields to map to in the Destination Mapping in Integration Manager in the Internet Information section. Any ideas? Thanks.

  • Suggested answer
    Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,625 Super User 2025 Season 2 on at

    You might want to consider using Table Import.  Have a look at SY01200 in the company database.  That's where email addresses are stored.

  • Richard Wheeler Profile Picture
    75,848 Moderator on at

    There are no equivalent fields in GP for these. These internet address are simply per individual. The 'To' and 'cc' addresses come into play per email not per individual.

  • Suggested answer
    Ian Grieve Profile Picture
    22,784 on at
    These fields weren't made available to Integration Manager; I'd suggest having a look at extending your integration with some VBA to populate the data in the After Document script.
  • Suggested answer
    Heather Roggeveen Profile Picture
    9,146 on at

    The other thing to do is to map to the existing fields and then in SY01200 use an update script:

    UPDATE SY01200 SET EmailToAddress = INET1

    Once you have the records in the SY01200 table, you could then use an insert script to take care of the remaining EmailCcAddress and EmailBccAddress.

    Mail merge in Word can be used to populate the script as needed.  

    I have a video on Mail Merge (related to creating macros - another good way of updating data) if it is of use:  www.youtube.com/watch

  • Community Member Profile Picture
    on at

    I couldn't get table import to work. Get telling me there were mandatory fields even though they don't need populating when you look at other records already completed...

    I don't understand the VB post, how is that done?

  • Ian Grieve Profile Picture
    22,784 on at

    Daniel, I'll see if I can knock together an example for you later today or tomorrow.

  • Suggested answer
    Ian Grieve Profile Picture
    22,784 on at

    Due to problems on my dev box I haven't been able to test the following as a whole although the VBA is based off another one I did recently and the SQL has been used individually.

    The following goes against the Before Integration script hook:

    ' BEFORE INTEGRATION
    Dim oCon
    Dim sINTERID
    
    Set oCon = CreateObject("ADODB.Connection")
    oCon.ConnectionString = "database=" & GPConnection.GPConnIntercompanyID
    GPConnection.Open(oCon)
    
    SetVariable "gblConn", oCon
    

    The following goes against the After Document script hook:

    ' AFTER DOCUMENT
    Set oCmd = CreateObject("ADODB.Command")
    With oCmd
    	.ActiveConnection = GetVariable("gblConn")
    	
    	.CommandText = "SELECT TOP 1 COUNT(EmailToAddress) AS Count FROM SY01200 WHERE Master_ID = '" &  SourceFields("VendorEmails.VENDORID") & "' AND ADRSCODE = '" & SourceFields("VendorEmails.ADRSCODE") & "'"
    	Set rsQuery = .Execute
    
    	If Not (rsQuery.EOF and rsQuery.BOF) Then
    		If rsQuery("Count") > 0 Then
    			.CommandText = "UPDATE " & _
    								"SY01200 " & _
    							"SET " & _
    								"EmailToAddress = '" &  SourceFields("VendorEmails.EmailToAddress") & "', EmailCcAddress = '" &  SourceFields("VendorEmails.EmailCcAddress") & "', EmailBccAddress = '" &  SourceFields("VendorEmails.EmailBccAddress") & "' " & _
    							"WHERE " & _
    								"VENDORID = '" &  SourceFields("VendorEmails.VENDORID") & "' AND ADRSCODE = '" & SourceFields("VendorEmails.ADRSCODE") & "'"
    				
    			Set rsUpdate = .Execute
    		Else
    			.CommandText = "INSERT SY01200 " & _
    								"(Master_Type,Master_ID,ADRSCODE,INETINFO,EmailToAddress,EmailCcAddress,EmailBccAddress) " & _
    							"VALUES " & _
    								"('VEN','" &  SourceFields("VendorEmails.VENDORID") & "','" &  SourceFields("VendorEmails.ADRSCODE") & "','','" &  SourceFields("VendorEmails.EmailToAddress") & "','" &  SourceFields("VendorEmails.EmailCcAddress") & "','" &  SourceFields("VendorEmails.EmailBccAddress") & "')"
    			Set rsInsert = .Execute
    		End If
    	End If
    	rsQuery.Close
    	Set oCmd = Nothing
    
    End With

    The above VBA assumes your integration record source is called VendorEmails and you have the following columns:

    • VENDORID
    • ADRSCODE
    • INETINFO
    • EmailToAddress
    • EmailCcAddress
    • EmailBccAddress

    The script checks if the email information exists and if it does then it does an update, otherwise it does an insert.

  • Suggested answer
    Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,625 Super User 2025 Season 2 on at

    Daniel, here's what the mapping needs to look like.  I tested this and it worked in my system.  One caveat - you can't use Table Import to update records, only insert.  Also, there is no data validation using Table Import.  If your source data is bad, you'll have bad data in SY01200, so make sure you manually validate your source data should you decided to use this method.  Take a back up of your database first, as well, just to be safe.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans