Well, after assuming it was a bad idea to rely on DEX_ROW_ID never changing, it is now officially a bad idea; David Musgrave has spoken on the Developing for Dynamics GP blog.
As David explains, DEX_ROW_ID was added when support for SQL Server was added to Microsoft Dynamics GP but is not guaranteed to always remain the same. For example, a change to the table structure during an upgrade could result in the DEX_ROW_ID changing. As it isn’t a fixed value, it should never by relied upon in customisations, integrations or custom code.
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.
Looking for support or consultancy with Microsoft Dynamics GP?
I no longer work with Microsoft Dynamics GP, but the last company I worked for was ISC Software in the UK; if you’re looking for support or consultancy services with Microsoft Dynamics GP you can contact them here.
1 thought on “Do Not Use DEX_ROW_ID In Customisations Or Integrations”