duCompanyVersions + Client Customization?

Question Status

Verified
Chad Bruels asked a question on 12 Oct 2017 3:20 PM

Twelve years developing for Dynamics GP and this is the first time someone has asked me to create a record in duCompanyVersions for the Dexterity customization we built for them.

I am only vaguely familiar with the duCompanyVersions table. Before I go adding a record to it, I want to make sure I know how I should do that and what I'm potentially impacting down the road. I understand this table is leveraged in the upgrade process, but I do not know how to anticipate my customization's records would do, if anything, to that process. What should I be doing with my customization to keep these records properly up to date as time goes on and patches and upgrades are applied?

Reply
Verified Answer
David Musgrave responded on 13 Oct 2017 1:57 PM

Hi Chad

I use this for all my products. It does not cause any issues with Dynamics Utilities having additional products in the table.

I update the record for system and company once tables have been installed/upgraded for that database.

David

Reply
Chad Bruels responded on 18 Oct 2017 9:23 PM

Thank you, David.

Do you create records in the db_Upgrade table as well?

Reply
David Musgrave responded on 18 Oct 2017 9:27 PM

Hi Chad

Nope, just duCompanyVersions.

My upgrade code can bring any old format to the current format and does not need duplicate table definitions kept in Dexterity.

David

Reply
Chad Bruels responded on 18 Oct 2017 9:33 PM

I have request to also create records in db_Upgrade and I am considering why it would be desired. The client sites our product having "no version control in DYNAMICS..db_Upgrade". Can I trouble you for a brief background on this table which might aid me in understanding its purpose and interpreting the request I face?

Reply
David Musgrave responded on 18 Oct 2017 10:07 PM

Hi Chad

db_Upgrade is specifically used by Dynamics Utilities during the upgrade process. Unless you are writing your own code to integrate with Dynamics Utilities, I would suggest leaving this table alone.

Adding records into it for products not supported by Dynamics Utilities could cause upgrade errors.

David

Reply
Chad Bruels responded on 19 Oct 2017 8:59 AM

Thank you for that confirmation.

As always, your depth of knowledge and time shared with this community is most appreciated.

Reply
Chad Bruels responded on 19 Oct 2017 9:39 AM

This is interesting. I believe further discussions have revealed what the client is truly looking for in version control. They have something like 20 terminal servers and wish to easily determine the version of our product installed on each so as to ensure a consistent deployment across all. Let the brainstorming commence - I need more tea.

Reply
David Musgrave responded on 19 Oct 2017 9:44 AM

Rockton Software's Toolbox has VersionPro which can check dictionaries installed.

Also, in your code, you can check the duCompanyVersions table and show a dialog if the server has a later version in the tables than the dictionary installed.

David

Reply
Verified Answer
David Musgrave responded on 13 Oct 2017 1:57 PM

Hi Chad

I use this for all my products. It does not cause any issues with Dynamics Utilities having additional products in the table.

I update the record for system and company once tables have been installed/upgraded for that database.

David

Reply