You’re offline. This is a read only version of the page.
I am working through all the steps necessary to upgrade from 2010 to 2013. It's been a long and often non-obvious road.
The next part I am stuck on are the integrations. We have dozens I need to be able to work with. The Export/Import tool doesn't act at all like what I would expect, and the main blog post everyone keeps referring to (Mahmoud Daoud) gives zero context.
Can someone please explain the implementation of export/import for custom integrations using Integration Manager? It makes zero sense to me and I REALLY don't want to have to export/import these one at a time...
*This post is locked for comments
It is not that I am not appreciative of the efforts nor do I doubt that your instructions work, it is that I am literally starting from zero knowledge base and the instructions I keep getting here omit several key pieces of information that seem trivial to you but are missing from my vocabulary.
I understand that you want me to move SOMETHING from the production server to the test server, but I don't know A) WHAT that something is, B) WHERE to look to find it, or C) where to copy it to.
Yep,
I'm with Jonathan. Just paste a copy of the IMD/MDB file on your test server. Run through Soma's steps, but point to the copied database in the Options window. You will need to change the location your integration manager is pointing to, as Soma instructed.
The integration manager has a couple of adapters you can use: the 'standard' adapter and the 'e-connect' adapter. You need to look at each integration and determine the adapter. With the e-connect adapter, the target company is hard-coded.
One other thing you need to look at are your data sources, are they pointing to a location on your test server? Next, do you have any VB Script in your integrations? Look at each of these scripts to see if they acquire or send data from/to the correct database or file.
Although you may have changed to location of the .mdb/imd file in the Options menu, it could still be overridden by the entries in the users C:\Users\USERNAME\AppData\Roaming\Microsoft\Microsoft Dynamics GP\12.0.0.0\IMUser_Data.xml file. If you are using the sample data or user translations, you also want to look at the IMUser_Translations.xml file in the same table.
Other pathing you need to check is the location of the integration logs.
Moving and testing integration manager can be quite complicated, depending on the sophistication of your integrations. Doing a step-by-step on this forum is really beyond the scope. Suffice it to say, I think you need to get the help of someone intimately familiar with integration manager if you want to test it properly.
Kind regards,
Leslie
First please understand we are trying to help here. What you need to do is make a copy of your IMD/MDB file from production and move it to your test environment. The integrations are stored in this file as this is a access database. After you do that go into Integration Manager and point to this IMD/MDB file you have brought over. Then do the instructions that Soma graciously provided.
I don't want to convert my live information just yet. That's why I'm working on a test box.
After creating the test server, I restored backups of the Dynamics and company databases to SQL Server. Then I installed Dynamics (the client) onto the database server. But apparently, (like forms and reports), you can't really make backups of the integrations and restore them like you would a database. (Something I wish Microsoft would enable). So I had to manually import all the modified reports onto the test server. Apparently, I have to do the same with the Integrations, and I'm trying to understand the mechanism for #1 How they are currently stored and #2 How do I get them onto the test box (and upgraded) so I can verify they still work after the upgrade.
I am asking that if you respond to this thread, DON'T SKIP STEPS. Don't assume I know anything with respect to the mechanisms of GP, because I don't. I am willing to learn, but I am starting from ground zero.
..
Open your Integration Manager in GP 2010 machine, then go to Tools-->Option and note the Default Integration Manager Database path under General Tab.
Now open the Integration Manager in GP 2013 machine, go to Tools-->Convert Database and select the database name which you have mapped in GP 2010 and then click convert database. Then go to option menu and map the converted Database name and check whether the integration are available from your existing dynamics system.
Hope this helps!!!
You don't really need to do anything as far as the upgrading of your IMD/MDB file. Have you tried just to point IM 2013 to your IMD/MDB file on the pervious version?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (