The following information includes common problems that can occur when you run an integration.
Situation When I run an integration, the data for a child recordset in the destination is not integrating.
Solution Be sure that the Record Source is set to the proper source. In the Destination Mapping window, select the child recordset that is not integrating. Choose the Options tab. The Record Source option should be set to a valid source query. If it is not, click in the Source column and select the proper source query or recordset from the list.
Situation When I run an integration, no errors occur but the integration fails after 10 warnings.
Solution New integrations have a default setting that causes them to fail after 10 errors or 10 warnings. To change this, open the Integration Properties window and set the number of warnings to a higher number.
Situation My integration runs slowly.
Solution There are several changes you can make to your integration to increase the performance of the integration.
The most appropriate columns to sort by for performance reasons would be those involved in relationships with other source queries in the integration. For example, if a relationship between two sources is based on the DocNumber column, sorting both source queries by that column will increase performance.
This only works if the sorting options are specified in Integration Manager. The performance of the integration won’t increase if the data is sorted by other means, such as specifying an “order by” clause in the SQL text for Advanced ODBC or using a view or stored procedure that sorts the retrieved data.
Situation I have a script in an integration that uses the “Execute” syntax. When I run the integration, I get a script error with the message “Expected Statement.”
Solution This is a known issue with VBScript version 5 and Integration Manager. The fix is to fully qualify the Execute method by adding “Integration.” before the Execute statement.
Instead of this: