Skip to main content

Changing the Dynamics GP Data Source in the Jet Data Manager

Overview

In some situations it is necessary to reconfigure the Jet Data Manager so that it extracts data from a data source other than the one that was originally configured.

Examples of this would be when:

  • the data source has been relocated to a different server
  • the ERP system has been upgraded and there is a new database that needs to be utilize
  • the Jet Data Manager was originally connected to a test or development environment initially and is now being connected to the production database.

Process

  1. Open the Project in the Jet Data Manager

    Since the data source needs to be changed in the project itself, the user will open the Jet Data Manager and open the desired project.

  2. Expand Data Sources in the Project

    The user will expand the Data Sources node on the desired Business Unit within the Jet Data Manager. This will show all of the data sources currently being used in the project.

  3. Edit the GP Data Source Provider

    The user will right-click the GP data source (in this example it is named GP) and select Edit Dynamics GP Adapter. This will open the Dynamics GP Adapter window.

    mceclip1.png

    The user will change the Server Name and Database properties to reflect the new data source that will be used. The database selected should point to the GP DYNAMICS database, not to an individual company database. The companies will be specified in the next step of this article.

    Click OK to close the window once these have been specified.

  4. Synchronize Companies

    The user will then right click the GP data source again and select Synchronize Dynamics GP Companies. This will synchronize the companies in the Jet Data Manager to match the companies in the new GP database. A Company Synchronization Options window will appear.

    mceclip2.png

    The user should leave the default "By Company Name" checked and click Synchronize. The GP Companies window will appear with a list of the current companies in the GP database. Check the "Use" boxes for all companies for which data should be brought in. The Template Company at the top needs to be set to be one of the companies that has the "Use" box checked. Click OK.

    mceclip4.png

  5. Synchronize Database Objects

    The user will then right click the GP data source and select Synchronize Data Source. This will synchronize all necessary database objects (such as tables, fields, and option values) from the new data source to the Jet Data Manager.

    The following window will appear during the synchronization process:

    Once synchronization is complete the Jet Data Manager will display any changes that have occurred in the tables and fields currently being used in the project.

  6. Edit the GPSQL Data Source Provider

    The user will right-click the GPSQL data source (in this example it is named GPSQL) and select Edit SQL Server Data Source. This will open the Edit SQL Server Data Source window.

    The user will change the Server Name and Database properties to reflect the new data source that will be used.

    The database selected should point to the GP DYNAMICS database, not to an individual company database. This should be the same DYNAMICS database that was selected in the previous steps. Click OK to close the window once these have been specified.

  7. Synchronize Database Objects

    The user will then right-click the GPSQL data source and select Synchronize Data Source. This will synchronize all necessary database objects (such as tables, fields, and option values) from the new data source to the Jet Data Manager.

    The following window will appear during the synchronization process:

    Once synchronization is complete the Jet Data Manager will display any changes that have occurred in the tables and fields currently being used in the project.

  8. Deploy and Execute the Project:

    After the new data source has been configured and synchronized the final step is to deploy and execute the project against the new database. This can be achieved by right clicking the project node in the Solution Explorer and selecting Deploy and Execute:

    The user will then click the Start button to start the deployment and execution process.

Was this article helpful?

We're sorry to hear that.