July 22, 2010 at 14:43
filed under Dynamics AX
Tagged Application, Dynamics AX, hotfix, Roll up
Hi all!
There seems to be a problem with the recently released RU5 for Dynamics AX 2009 SP1.
Dynamics AX clients are supposed to be backwards compatible, so you can always use the latest client, even if you want to connect to an application with a lower version (e.g. AX 2009 RU4 client to AX 2009 RU3 application). (Edit: Read comment #4 by Florian Dittgen)
But when I tried to connect to an AX 2009 RU3 application (5.0.1500.1313) after I updated my client to RU5 (5.0.1500.2985), it didn’t work.
Dynamics AX only shows the first record in the forms when you use that combination, as you can see in the screenshot below.
When you connect using a RU4 client (or RU3), there is no problem at all.
You can uninstall a hotfix rollup from the Add/Remove software screen in the windows control panel if you want to.
I prefer to duplicate the client folder each time I upgrade it so I have all client versions available.
Just fire up bin\ax32.exe for the version you want and you good to go :-).

Kenny Saelen
on July 22, 2010 at 16:02
I actually noticed this one today !
I think the problem seems to be with the extra method added to the grid control to enable / disable the automatic resizing of the columns for performance reasons..
Luegisdorf
on July 23, 2010 at 11:25
Confirmed, had the same probleme here, but in a funny way the effect only concerns some tables while on other tables all works fine.
To run concurrent client versions is a good idea. And with the SmartStart 3000 user doesn’t need to decide which client executeable has to be used ^^
kamal
on July 26, 2010 at 22:09
I did have this problem today..but for me the case was strange. The App version and Client version were matching with each other still we had the same situation.
When we examined we found that all the query from the form were suffixed with select firstfast …. so strange finally we ended up re installing everything….
Florian Dittgen
on August 8, 2010 at 11:52
Hello Klaas,
You wrote that Dynamics AX clients are supposed to be backwards compatible, but I don’t agree to this. Ax clients are only compatible (and supported by MS) to the AOS if both have the same kernel build. Until now the clients could run in most cases with a different build, but this happend more by accident then by design. This is the reason why future Ax version will explicitely check this and respond with an exception if the builds are different.
Cheers,
Florian
Klaas Deforche
on August 8, 2010 at 12:15
Hi Florian,
Thanks for your comment and clearing things out.
It seems that I was misinformed about the supposedly backward compatibility.
Good to hear that there will be a check on this in future AX versions. That should make a lot of people’s jobs easier :-).