Microsoft Dynamics Integration Manager Guide

As a data integration software and tool, Microsoft Dynamics Integration Manager can be used to extract, validate, transform, and transfer data among organization’s business applications, eliminating the need to re-key data. Through Integration Manager (IM), organizations have a cost-effective option to integrate data without specialized programming knowledge or knowledge of databases and programming interfaces.

The integration manager offers a safe and easy to use platform for integrating data between your business applications. Data integration means extraction of data from databases or source applications and bringing it into a destination. Data integration into the Dynamics GP application can be from e-commerce solutions, external business databases, or any other data file types.

Microsoft Dynamics Integration Manager Guide

1. Installing and Starting Integration Manager

Integration Manager Overview

Common Terminologies

  • Source: where the information for integration comes from (i.e. a database like ODBC (Open Database Connectivity source), or comma- or tab-delimited file).
  • Source adapters: these connect to sources, filter, and extract data to be passed on to the IM engine for processing.
  • Integration Manager engine: with the help of a destination adapter and a source adapter, the IM engine helps in mapping and integrating the source data into the relevant destination.
  • Destination: where the processed information is to be integrated.
  • Destination Adapters: perform data validation before integrating it into the destination file, database, or application.
  • Destination mappings: define mapping of source data into the destination.
  • Query: A request for information.
  • Query Relationship: communicate to the IM how various queries work together.

Installing Integration Manager

All system requirements should be met before installing Integration Manager, including having administrative rights, Microsoft Dynamics GP, eConnect, Microsoft Internet Explorer 5.0 or higher, and Microsoft Data Access Components. Install and register Integration Manager, and then store registration keys in the file “IntegrationManager.ini”

Using Integration Manager

To start Integration Manager, go to Start >> Programs >>Microsoft Dynamics >> Integration Manager >> Integration Manager, or start it from the Dynamics GP application. Create a new database from Tools>> Create Database. The Integration Manager Toolbar and Integration Manager Menus allow you to perform various functions.

2. Building and Running Integrations

Creating Integrations

The integration process begins with creating the integration containing the source and destination info. You may choose to define a new integration or just use an existing one.

Adding Sources

After creating an integration, the next step entails adding your sources to define which data from the source will later be integrated into the destination.

Creating Query Relationships

When you use text sources and ODBC in your integration, IM will issue queries to retrieve data from the sources. Using more than one ODBC will require you to create relationship among sources.

Data Types

Use the most appropriate data type when adding sources. These data types include Boolean, Currency, Date, Enumeration, Integer, Long Integer, Numeric, String, and Time.

Adding a Destination

After adding a source, you may add your destination to indicate where the information should go.

Creating Mappings

The next thing to do after adding your destination is to map your source data to the destination. The function of a destination mapping is to describe the source of each field in the destination of the integration.

Running Integrations

After the above processes, now get ready to run the integration to import the source data into the selected destination.

Troubleshooting Integrations

If the integrations are not functioning properly, you may consider troubleshooting. Common problems with sources include missing field value data, ODBC errors, missing/extra rows, or fields, mapping problems, integration problems, slow integrations, script error, and incorrect data integrated.

3. Managing Integrations

Modifying Integrations

Microsoft Dynamics Integration Manager lets you use integrations from many other databases. Import and export integrations all from within IM and even modify various components for use in creating integrations.

Pathname translations

Here you can define substitutions for pathnames defined in the IM database file.

Managing Logs

IM creates a log file where you can find detailed information regarding the outcome of integration.

Compacting the Access database

Removing information from integrations means removing from the Access database file, but this process does not fully reclaim the space utilized by the file. Microsoft Access can be used to compact the IM database (IntegrationManager.mdb).

Using Integration groups

Integration groups allow you to perform multiple integrations in succession overnight.

Running Integrations from the command line

Starting integration groups or integrations from the command line is used when scheduling integrations for begin as predefined times. But you must run Microsoft Dynamics GP and record a macro to perform the required login process the Dynamics GP before you begin this process. Use IMRUN.EXE.

Advanced ODBC source queries

They utilized a SQL statement when retrieving information from ODBC data sources. So, basic knowledge of SQL is a prerequisite.

4. Adapter Reference

Adapters & Destination Mappings

You can decide which adapters you want to use with IM. The adapters include Dynamic GP destination adapter, XML source adapter, and Dynamics GP eConnect destination adapter. There are various modules in the Dynamics GP adapter: the Financial Module, the Payable Management module, the Receivables Management, The Sales Order Processing, the Payroll module, the Inventory module, and the Setup module. XML adapter in Integration manager allows you to move XML data into Dynamics GP very easily.

5. Using VBScript

Scripting capabilities allow you to customize integrations. Extend the functionality of IM by adding scripts to integration events and various fields.

Using scripts

Included in IM is VBScript, which you can use to attach scripts that will automate integrations. You can all attach code to run while various actions are being performed by IM.

VBScript objects

A combination of data and code that may be treated as a single unit.

Functions

VBScript comes with many in-built functions, which are a subset of the ones in Visual Basic. The functions include CancelDocument function, CancelIntegration function, ClearVariables function, DocumentIsNew function, DocumentNo function, Execute function, GetVariable function, LogDetail function, LogDocDetail function, LogDocWarning function, LogWarning function, PlaySound function, and Setvariable function.

Conclusion

When you decide to create an integration, you have to specify sources, destinations, as well as destination mappings. Sources typically include the data you want to integrate into your destination within the dynamics GP, while the destination mappings where items from the source data go in the destination. Microsoft Dynamics Integration Manager eliminates the need for re-keying data.

Michael Taylor
Michael is the Lead Author & Editor of DynaMe. DynaMe is a blog focused on cloud based Microsoft Dynamics.
Michael Taylor on sabtwitterMichael Taylor on sablinkedinMichael Taylor on sabgoogleMichael Taylor on sabfacebook