Done
Details
Assignee
Andrei MakarankaAndrei MakarankaReporter
Craig McNallyCraig McNallyTester Assignee
Craig McNallyCraig McNallyPriority
P2Story Points
1Sprint
NoneDevelopment Team
ThunderjetFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Andrei Makaranka
Andrei MakarankaReporter
Craig McNally
Craig McNallyTester Assignee
Craig McNally
Craig McNallyPriority
Story Points
1
Sprint
None
Development Team
Thunderjet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 27, 2020 at 5:09 AM
Updated April 6, 2020 at 10:06 PM
Resolved March 30, 2020 at 7:12 PM
Overview
When upgrading from v3.0.1 (Edelweiss) to v3.1.0 (FameFlower), data migration scripts for invoices and vouchers fail because of a foreign key constraint.
The issue is that we have data migration scripts which update invoice and voucher records to add a new required field (batchGroupId). The value we use for this is the "default" batch group, which we insert as "system" data - akin to reference or sample data, but always loaded. Since that data doesn't get loaded until after the db migration scripts run, the batch group doesn't exist when the migration scripts are run, causing them to fail because they violate the FK constraint.
Relevant log snippet: