Migrate to v5 tweaks
- On install v5 failure, make sure DB is reset back to a state where messenger doesn’t think an upgrade is happening. Previously a failure would break messenger
- Migrator changes : see migrator changelog for details.
Migrate to v5 tweaks
No functional changes, just tweaks to v5 migration stuff. This version is first post pilot upgrade candidate and could in theory be the last ever version of v4 c9 (likely there will be a couple more updates to cope with oddball data in some v4 systems as they are encountered).
Includes DB changes, you need to log all terminals out during upgrade
This version fine tunes fixes payroll liability changes outlined in v5.1.10. The liability fix was incorrectly tagging liability codes as input taxed. This ver removes this tagging as it is incorrect.
Includes database changes. You need to log all terminals out during upgrade
Includes DB changes. You need to log all terminals out during upgrade
Fixes
This version reworks how debtor/creditor/custdeposit txn records are managed. Migrator is working correctly, but newly created txns in c9 after migration were not presetting item/loc/origin style tracking. Generally not a functional issue, but will cause some grief down the road when we go for v5.2 changes. Some minor functional issues. e.g. on workshop payment to invoice, it would say ‘payment’ at bottom of invoice, not the correct ‘On Account Owing’.
Another issue to fix is that v5 online backups downloaded are not restoreable. Data is fine, but generated schema is busted and needs to be manually tweaked before installing. (Incorrect priming/inferencing of primary key sequences on v4 txn tables).
Includes DB changes you need to log all terminals out during upgrade
Includes DB changes you need to log all terminals out during upgrade
Version 4.890 was supposed to include the following changes but what was deployed didn’t actually include them. This update backfills / fixes this up. Specifics:
Bonus changes:
Includes DB changes, you need to log all terminals out during upgrade
Includes DB changes, you need to log all terminals out during upgrade
A few tweaks around migration to v5 + online backups. Backups are supposed to detect upgrades and not try to backup data until finished but this wasn’t working 100% for v5 migrate resulting in backup issues on migration if migration is performed on a computer other than the messenger computer. V5 database contains some slight variations that require changes to backup codebase (physical location of primarykey field on v5 tables shifted from start to end of table definition), these changes are now pre-baked into this version of v4 to further minimize possible niggles on migration if there is some other vector in play which causes an un-migrated v4 migrated messenger to try and backup v5 data prematurely.
Other
v5.1.5 only