So one of our customers has a customization where we added a field for them. They will need to upgrade to the newest version of Acumatica soon. All this customization did was add a field to an AP window. How is that customization field data stored in the database? Could it be lost during an upgrade? Just want to make sure I have a good understanding of this before giving them the go ahead.
Solved
Field Customizations Upgrade General Questions
Best answer by Laura02
Hello,
In addition to recommendations above from
In my experience, some customizations require upgrades, and some do not. In general, customizations are less likely to need upgraded code when the customizations are small and there isn’t a large gap between your customer’s prior version and their new Acumatica version.
At Klear, we follow these step-by-step procedures when a customer upgrades:
- Before requesting a Sandbox, we export Klear-created customizations, one at a time, and save the exported files.
- When the Acumatica Sandbox site is provided, we sign in and publish Klear Customizations to all tenants on the sandbox site in Customization Projects screen.
- If they publish successfully - no further work is needed for the customization.
- If publishing fails, we contact our internal developers to request an upgrade for the customization to be compatible with the new Acumatica version.
If you want to test in advance, you can try importing the customer’s customization file(s) to a demo tenant of the same version your customer will update to, with similar features activated and see whether it publishes and works as expected.
Laura
+15
If this field was storing a value then it is in the database and wont be affect by the upgrade so once you republish the field will be available.
Dermot Comerford
Hi
The customisation is added through a DAC extension, depending on what field type you used, either DBTableColumn, NameValuePair, or NonPersistedField.
DBTableColumn adds a DB script adding the field to the database, which means the field is stored in the database.
I am not too sure of NameValuePair, and NonPersistedField is not stored in the DB.
An upgrade should not do anything to a custom field. It definitely will not be lost, unless you delete the customisation project.
Custom DACs need to be marked with PXBqlTable from 24R1 onwards but DAC extensions don’t need this.
Hope this helps,
Aleks
https://www.linkedin.com/in/aleks-iwan-mbcs-03705b240/
+19Hello,
In addition to recommendations above from
In my experience, some customizations require upgrades, and some do not. In general, customizations are less likely to need upgraded code when the customizations are small and there isn’t a large gap between your customer’s prior version and their new Acumatica version.
At Klear, we follow these step-by-step procedures when a customer upgrades:
- Before requesting a Sandbox, we export Klear-created customizations, one at a time, and save the exported files.
- When the Acumatica Sandbox site is provided, we sign in and publish Klear Customizations to all tenants on the sandbox site in Customization Projects screen.
- If they publish successfully - no further work is needed for the customization.
- If publishing fails, we contact our internal developers to request an upgrade for the customization to be compatible with the new Acumatica version.
If you want to test in advance, you can try importing the customer’s customization file(s) to a demo tenant of the same version your customer will update to, with similar features activated and see whether it publishes and works as expected.
Laura
Laura ~ Klear Systems, Inc. Irvine, CA. ~ Click my logo to Follow me ~
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.