Sorting Records in Integration Manager v10.

After performing an upgrade to IM v10, from a previous release, users and developers alike must be aware that records will not automatically sort in the same order they appear in the file, thus making visual comparisons between source files and GP a bit more difficult.

To overcome this issue, open the Microsoft.Dynamics.GP.IntegrationManager.ini file found under your Integration Manager installation folder and change the UseOptimizedFiltering value to False.

This issues has been documented under KB article 924857.

MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Anonymous said…
Close IM for the change to take effect
October 5, 2010 at 10:56 AM
Mariano Gomez said…
Anonymous,

Thanks for the additional step.

MG.-
October 5, 2010 at 5:31 PM
Unknown said…
When I make this change, no transactions are integrated. The invoice is created with no lines items. Any fix for this?

Thanks!
Derek
March 28, 2011 at 2:07 PM
Mariano Gomez said…
Derek,
You will also want to do the same thing for the IMRun.ini if your users are running the integration from there.

MG.-
March 28, 2011 at 2:52 PM
Anonymous said…
Thank you so much for the post. The sorting records issue had been bugging me for so long and IT Help Desk at work couldn't help.

Thanks again.
Regards,
November 16, 2011 at 12:06 PM
Anonymous said…
Does anyone else have the problem where this setting causes the integration to break. i.e. the detail lines on a JE import will not import. The header comes in, but the lines do not.
November 6, 2013 at 2:16 PM
Anonymous said…
Yes, I have that issue as well. No lines on the JE after making this change.

-Matt
December 11, 2013 at 10:12 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more