hi,
When I asked for a help with customization package creation, it was told to me that Acumatica where this package will be created must be same version as other Acumatica instances where this package will be used.
Is the any way to create universal package for all Acumatica version or maybe more simple process that switch to other Acumatica, recreate package for each version ?
Best answer by AaronB
View original
+1
Hello Ivan,
Customization packages can be published on any version, forwards or backwards in most cases.
Sometimes Major releases (22r1, 22r2, etc) can contain changes in method signatures or functionality that can break compatibility with older customizations.
In that case you will need to update your code to match the changes and release a new fixed customization package for that version and up. Often times it is just a few lines of code to fix.
However, Acumatica Snapshots made from the “Tenants” screen are version specific and can be updated by publishing the snapshot, doing a website upgrade using the Acumatica installer, and creating a new snapshot export from the updated website.
Hi
But part of this is already seen in the Compiler Validation when you try to publish. When you try to publish the old package (developed for older version), the compiler Validations tool on the “Publishing” action in the the “Customization Projects” screen already specifies that the old fields or methods are not found. This provides a clear indication of the changes required on the customization to be published successfully.
Hope this helps for your to create an idea in the respective section of this portal.
Thanks
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
