SyteLine 8 and 9 to SyteLine 10 Technical Upgrade Checklist

Start with the customisation inventory

Every upgrade problem traces back to a customisation nobody listed. Use FormSync to list customised forms, IDO Custom Assemblies to list extension class assemblies, and sys.procedures to list EXTGEN_ procedures, which SyteLine uses to extend base stored procedures. Add custom triggers, Uf_ user fields and user extended tables, event handlers, Background Task Definitions, custom reports, replication rules and BOD integrations. For every item, record owner, purpose and whether it is still used. Retiring a dead customisation is the cheapest upgrade work you will do. If you cannot find the source code for an extension class assembly, flag it now: you will need to recompile it.

• FormSync: customised forms
• IDO Custom Assemblies: extension class DLLs
• EXTGEN_ procedures: extended base logic
• Uf_ fields and user extended tables

Carrying customisations forward

FormSync merges WinStudio form customisations into the new form versions; it handles form definitions, not IDO metadata or SQL code. IDO metadata changes move with App Metadata Transport. Extension class assemblies must be recompiled against the Mongoose DLLs of the new release and re-imported, because they reference framework classes that change between versions. Each EXTGEN_ procedure was a copy of a base procedure with your change applied; the base procedure has changed, so diff the old base, your EXTGEN and the new base, then re-apply the change to a fresh copy. After services are configured in Configuration Manager and Service Configuration Manager, use LogMonitor while opening forms to catch broken references fast.