Previous changes to permit rollback of units with deal deposit involvement made things a bit too loose, you could manipulate unit deposit txns via Business -> activity in ways which are not yet supported in v5.  Tightened things up again.

Bugfix : rollback a unit sale which uses deposit captured on deal would fail to rollback.  Now fixed.

More tweaks to v5 migration.

Tweaks and fixes

• Delete a job that was previously invoiced would fail with a 'save mode not defined' error. Now fixed
• Subtle rounding issues in some circumstances involving certain spares discounts & c9 setup where spares rounding is set to 0.00. Would trigger journal balance errors. Now fixed. Non update workaround involves reconfiguring c9 so it rounds to 0.01 (which is what 0.00 is functionally supposed to be equivalent to).

Tweaks to tender / post invoice screen for spares. Display invoice details as part of tender display, invoice# etc so dealer knows what no# was issued when they do not select print invoice.  For quotes/reserves, tender details are greyed out but invoice particulars are still displayed.

More migration tweaks

Tweaks and fixes

• Spares quote : was not printing totals now fixed
• Fine tune no instruments mode : open up tender screen
• Fine tune clerk key behaviours. Was asking for clerk keys always even when clerk keys are partially/fully disabled in some areas. Now fixed.

Tweaks and fixes

• Units quotes broken in this ver of c9. Now working again. Specifics:
  • Quote creation broken
  • Printing existing quotes broken
  • Converting existing quotes to an invoice was fine tho.

V5 migration tweaks

• Old BAS forms would reference defunct cash GST code causing migration to fail. Now patched
• More work on patching sublet migration.
• Couple more unmatched txn types
• Cope with bug from 6 years ago where in a multi unit sale/purchase one of the units could be rolled back without affecting others

V5 migration tweaks

• For very old c9 clients, 1 or 2 decades old who never have had to restore from online backups, migrator would fail because of very subtle non functional differences between an old database that is decades old vs one restored from backups. Now sorted (not nullpointer guards on db columns)
• A few minor odd variations in historical data, doucmented in gitlogs
• Tweaks to sublet migration, some bad sublet data where sublet status is mismatched from general ledger causing issues. Fixed by realigning the sublet with GL