Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you run an integration that uses VBScript code after you upgrade to Integration Manager for Microsoft Dynamics GP 10.0: “DOC 1 ERROR: Object required”

Error message when you run an integration that uses VBScript code after you upgrade to Integration Manager for Microsoft Dynamics GP 10.0: “DOC 1 ERROR: Object required”

Summary

This article lists the code that must be changed from the RetrieveGlobals format to use the new ADO connection objects that were added in Integration Manager for Microsoft Dynamics GP.

↑ Back to the top

Symptoms

You upgrade to Integration Manager 10.0. When you run an integration that contains VBScript code, you receive the follow error message:
DOC 1 ERROR: Object required:

DOC 1 ERROR: Error Executing Script ‘<Integration_Event>’ Line xx:”
Note In this error message, "<Integration_Event>" is the Integration Manager event that contains the VBScript code.

↑ Back to the top

Cause

This issue occurs if RetrieveGlobals VBScript code exists in one of the scripts in the integration.

↑ Back to the top

Resolution

To resolve this issue, update the VBScript code to use the new GPConnection object, and then update the lines that set up the ADODB.Connection object. The RetrieveGlobals userinfo object is no longer used in Integration Manager 10.0.
  1. Locate the following line: 
    uom = SourceFields("ItemPriceUpdate.UofM")
    Change this line to resemble the following:
    uom = SourceFields("Item Pricing Specific.UofM")
    Note When you make this change, the script is updated so that it is compatible with the Integration Manager 10.0 Inventory Item sample integration. This step is not typically required to update code to use the GPConnection object.
  2. Comment out the following line. This line is no longer required: 
    'Set userinfo = CreateObject("RetrieveGlobals9.retrieveuserinfo")
  3. Comment out the line that uses the userinfo object Connection method to return an ADO connection object. Then, add a new line to create a new ADO connection object that will be passed to the GPConnection object open method: 
    'Set cn = userinfo.Connection
    Set cn = CreateObject("ADODB.Connection")
  4. When you use the GPConnection object, you must specify the company database before you pass the ADO connection object to the Open method. To do this, comment out the line that uses the userinfo object intercompany_id method to set the DefaultDatabase property of the connection object. Then, add a new line that uses the built-in GPConnection object to specify the database as follows: 
    'cn.DefaultDatabase = userinfo.intercompany_id
    cn.ConnectionString = "database=" & GPConnection.GPConnInterCompanyID
  5. Pass the ADO Connection object that you set up in step 4 to the Open method in the GPConnection object so that it is ready for use. Add the following line: 
    GPConnection.Open(cn)
  6. Comment out the line at the bottom to release the userinfo object. This object was not created: 
    'Set userinfo = Nothing
Make sure that you do not change the rest of the code. You have to change only the lines of code that create and set up the ADODB.Connection object. The following code is the updated code. You can paste this code into the Inventory Item sample integration After Document script event.
'Integration Manager 10.0 VBScript code
'A similiar version can also be found in the Integration Manager Script Library
Dim cn, cmd, rst, userinfo, Item, uom

Item = SourceFields("Inventory Item Main.ItemNumber")
uom = SourceFields("Item Pricing Specific.UofM")

'Old Integration Manager 9.0 code
'Create the retrieveglobals object
'Set userinfo = CreateObject("RetrieveGlobals9.retrieveuserinfo")

'Create the ADO connection object using RetrieveGlobals
'Set cn = userinfo.Connection
'cn.DefaultDatabase = userinfo.intercompany_id

'New Integration Manager 10.0 code
Set cn = CreateObject("ADODB.Connection")
cn.ConnectionString = "database=" & GPConnection.GPConnInterCompanyID
GPConnection.Open(cn)


'Create the ADO command object
Set cmd = CreateObject("ADODB.Command")
cmd.ActiveConnection = cn


cmd.CommandText = "Update IV00101 Set PRCHSUOM = '" & uom & "' where (ITEMNMBR='" & Item & "')"
Set rst = cmd.Execute


'release objects
Set rst = Nothing
Set cmd = Nothing
Set cn = Nothing
'Set userinfo = Nothing

↑ Back to the top

More Information

The following is an example of an Integration Manager 9.0 VBScript code that uses RetrieveGlobals9.dll to create an ADO connection to execute an SQL statement to update the Default Purchasing UofM in an Inventory Item integration. The following code is added to the After Document event:
Dim cn, cmd, rst, userinfo, Item, uom

Item = SourceFields("Inventory Item Main.ItemNumber")
uom = SourceFields("ItemPriceUpdate.UofM")

'Create the retrieveglobals object
Set userinfo = CreateObject("RetrieveGlobals9.retrieveuserinfo")


'Create the ADO connection object using RetrieveGlobals
Set cn = userinfo.Connection
cn.DefaultDatabase = userinfo.intercompany_id


'Create the ADO command object
Set cmd = CreateObject("ADODB.Command")
cmd.ActiveConnection = cn


cmd.CommandText = "Update IV00101 Set PRCHSUOM = '" & uom & "' where (ITEMNMBR='" & Item & "')"
Set rst = cmd.Execute


'release objects
Set rst = Nothing
Set cmd = Nothing
Set cn = Nothing
Set userinfo = Nothing

↑ Back to the top

Keywords: kbexpertiseinter, kbprb, kbmbsmigrate, kbtshoot, kbexpertisebeginner, kbsurveynew, kb, kberrmsg, kbexpertiseadvanced, kbnosurvey, kbmbspartner

↑ Back to the top

Article Info
Article ID : 971837
Revision : 1
Created on : 3/3/2017
Published on : 1/7/2015
Exists online : False
Views : 83