I had a case recently where the customer's auditors were asking the customer to prove the version and build of Microsoft Dynamics GP was the same as the version they claimed it was. Basically, the auditor said "provide me proof that you are running GP X SP Y".
So during this case, I discussed a number of methods with the customer and let them choose what worked best for them. In this case, I was dealing with the customer's DBA, who did not have access to run the Dynamics GP client, so not all of the methods I provided would have worked for him.
Here is the list I came up with:
With all of these options you should be able to easily confirm your version and compare it against the Version Information Spreadsheets to identify the exactly release you are on.
I want documentation of Visual Studio Tools for Microsoft Dynamics GP 2013? can you help me.
That questions is not quite relevant for this post.
Anyway, just install Visual Studio Tools for Microsoft Dynamics GP 2013 from the \Tools\SDK\VS Tools folder of the DVD image. It has the manuals as part of the install.
Posting from Mark Polino at DynamicAccounting.net
This is a great post, and the links are very helpful as well. As part of an IT audit I required to show how many changes (upgrades/hotfixes/version changes) we have done to GP during a specific time. They would like this data to come from SQL. Are you aware of any table to tracks version changes?
The Dynamics Utilities tables track the previous version and the current version so they can perform upgrades, but they don't track a full history.
You could add triggers to the tables to write to a logging table when changes are made.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.