CentralCommand 2.0 Impact of Upgrade
These are possible impacts when upgrading to CentralCommand v2.0. | | | | GENERAL | | | Any user-defined menus do not convert correctly | Script to fix is being developed until fixed in upgrade. | | | | | Customization via VBA projects | May be impacted, must test | | | | | REPORTING | | | User-defined joins | May be impacted, must test | | | | | Database views | May be impacted, must test | | AG16 queries - syntax has changed | a) DB should now be entered as DATABASE
b) Some database fields have been expanded, may impact if field is used in an AG16
c) IF statements no longer are supported, if use currently will need to rewrite SQL to avoid using
d) There may be other changes that will be identified once start testing | | | | | Browser templates | May be impacted, must test. A utility has been provided to help identify browser templates affected. | | | | | Direct SQL calls from reporting tools (Excelerator, Agresso Report Creator, Crystal) | May be impacted, must test | | | | | FUNCTIONAL | | | Authorization groups | These are replaced with role-based security. A upgrade wizard has been provided to convert from authorization groups to roles. For customers with large numbers of groups it is recommended they are rebuilt manually. | | | |
Return to CentralCommand 2.0
|