NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
===Published templates===__NOEDITSECTION__
There might be templates that are created with an old version of {{IMSMANG}} and may contain errors that have been undetected in 5.08.04 but will not be working with V6.0. There are countries that have several hundred unused published templates. In order to avoid upgrade problems it is recommended to
# delete unused published templates ('''[[Used DEF template SQL |(query)]]''').# discuss with the country if some of the used published templates should be switched together ('''[[Used DEF template SQL |(query)]]''')
# check the names of the remaining templates for odd characters like @ #
# open the remaining templates in the Designer and verify that they are not multi-object e.g. Location and Land '''or''' two Accidents.
::*error message ''COPY fieldreportdesc'' means that it was not possible to load the table so the table is '''empty''';
::* error message ''ERROR: insert or update on table "fieldreport" violates foreign key constraint "fieldreport_fieldreportdesc_guid_fkey'' means that '''mandatory''' reference (FKs) between tables did not get created because of missing values in e.g. imsmaenum table. {{IMSMANG}} depends on that FKs are created.;
<li> The upgrade scripts will '''wrongly''' change enumvalues to Inactive and therefore the current values must be documented ('''[[Imsmaenum Duplicate fix | query]] ''') <li> The upgrade script will change ''Location point'' to ''Reference point'', run this '''[[Location point | query]] ''' '''before''' and '''after''' the upgrade.
<li> The upgrade scripts do not handle the subobjects that should be transformed into normal multi-selects well (2014-11-25/NAA).
Run these '''[[Check Detection Sample Sector VegetationRemoval | queries]] ''' in order to see if there are any records that have to be inserted manually.
<li> How many rows are there in the attachment table? If more than 0, then you have to verify that the attachments are included in the backup folder or instruct the country on how to handle them.
:: Note this issue should be fixed with 8 November build but check the logs anyhow.
# Therefore scroll through C:\IMSMAng\trayLauncher\trayLauncher.log even if the upgrade scripts have not thrown an error;
# Check if the upgrade scripts created duplicate enumvalues and if necessary fix them ('''mandatory''')('''[[Imsmaenum Duplicate fix Part 2| query]] ''' )(still happening with 8 Nov);
#: Duplicate enumvalues cause import issues i.e. empty fields, which are difficult to detect due to there are no error messages;
# Check if the upgrade scripts '''wrongly''' changed enumvalues to Inactive ('''mandatory''')('''[[Inactive enumvalue fix | query ]]''')(still happening with 8 Nov);# Location point should have been changed to Reference point by the upgrade script, run this query to verify ('''[[Location point | query]])''' to verify;
# Stop TrayLauncher;
# Start TrayLauncher;