Keeping the workorder table wouldn’t make sense because the IDs will not match the IDs of the new parent class ticket. I changed the table name from workorder to ticket_workorder to continue the naming convention.
For migration I have the following idea:
1. Export all WorkOrder objects using REST API because CSV-Export has problems escaping special characters in log entries.
2. Delete all WorkOrder objects to be clean
3. Run setup to change data model and database tables
4. Import WorkOrders
Any link like [[WorkOrder:123|my WorkOrder]] will not work anymore and history will be lost.
But how can I preserve inline images and attachments?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I successfully changed the work order’s parent class to ticket by redefining the whole class like this:
Keeping the workorder table wouldn’t make sense because the IDs will not match the IDs of the new parent class ticket. I changed the table name from workorder to ticket_workorder to continue the naming convention.
For migration I have the following idea:
1. Export all WorkOrder objects using REST API because CSV-Export has problems escaping special characters in log entries.
2. Delete all WorkOrder objects to be clean
3. Run setup to change data model and database tables
4. Import WorkOrders
Any link like [[WorkOrder:123|my WorkOrder]] will not work anymore and history will be lost.
But how can I preserve inline images and attachments?