Because all of the cr3 columns the crash diagram component uses are currently null until we do a back fill in the new crashes table, to test you will need to manually copy over some fields to a record.
In your db client, find a crash record in the new crashes table. Now find that same crash in the old atd_txdot_crashes table. Copy over the following columns from atd_txdot_crashes to the record in crashes: cr3_stored_flag (now a boolean instead of a string) and cr3_file_metadata
Now if you go to the crash details page for that crash id you should see the crash diagram there. You should also see a button to download CR3 pdf though you wont actually be able to locally.
Observe that the crash narrative is also pulling from the new table
Ship list
[ ] Check migrations for any conflicts with latest migrations in master branch
[ ] Confirm Hasura role permissions for necessary access
johnclary
commented
2 months ago
Associated issues
Closes https://github.com/cityofaustin/atd-data-tech/issues/17183
Testing
URL to test: Local
Steps to test:
nulluntil we do a back fill in the newcrashestable, to test you will need to manually copy over some fields to a record.crashestable. Now find that same crash in the oldatd_txdot_crashestable. Copy over the following columns fromatd_txdot_crashesto the record incrashes:cr3_stored_flag(now a boolean instead of a string) andcr3_file_metadataShip list