I have been playing with v11.7 of assyst and uncovered a few minor issues during the DB upgrade in a DEV environment (from v11.3.8), so I am just posting those for your information:The DB upgrade script fails when trying to add the stored procedure RESET_EVENT_HKS, which already exists in our schema.Mitigation: delete the stored procedure before running the upgrade.Long term solution suggestion: Ideally have the upgrade script always drop the stored proc prior to creation.Migration of forms will fail if they have multiple Web Custom Groups with the same label (in design mode), DB upgrade SQL fails with a duplicate error.Mitigation: before the upgrade, change the labels in design mode to make them unique, and then add the proper display label as a customization at the Global-English level.Long term solution suggestion: allow renaming of the label during DB migration to add a suffix, for example: “…_1”, “…_2” etc.

Question

assyst v11.3.8 upgrade to v11.7 - issues encountered

6 months ago
25 October 2023
1 reply
70 views

FantasticRhino
Do Gooder (Partner)
0 replies

I have been playing with v11.7 of assyst and uncovered a few minor issues during the DB upgrade in a DEV environment (from v11.3.8), so I am just posting those for your information:

The DB upgrade script fails when trying to add the stored procedure RESET_EVENT_HKS, which already exists in our schema.
Mitigation: delete the stored procedure before running the upgrade.
Long term solution suggestion: Ideally have the upgrade script always drop the stored proc prior to creation.

Migration of forms will fail if they have multiple Web Custom Groups with the same label (in design mode), DB upgrade SQL fails with a duplicate error.
Mitigation: before the upgrade, change the labels in design mode to make them unique, and then add the proper display label as a customization at the Global-English level.
Long term solution suggestion: allow renaming of the label during DB migration to add a suffix, for example: “…_1”, “…_2” etc.