Problem Importing when Automatic Deletion is set in Relationships Table

[jjjjp]

To allow for easy, simultaneous deletions of a parent and its children, I have started to take advantage of the following setting in the Relationship Table: "Delete related records in this table when a record is deleted in the other table." However, I import data from the user's version of my database into my developer's version by deleting all records from tables in my version and then adding records from the users' version while matching names. I noticed after an import that some tables were missing all their data and figured out that the cause was automatic deletion of records and unlucky order of imports. Because I had arranged the imports in alphabetical order, I was importing the parent (workshop) after its children (team members, offerings), and the children got wiped out because of the cascading effect of the initial deletion of workshops.

 

The ideal solution would be to suspend the cascading deletions set up in the Relationship Table while importing, but I gather that is impossible. What are best practices for avoiding deletion of records while importing? (1) Be ultra-methodical about how one orders imports? (Do the rules against circularity in the Relationship Table guarantee that there is always an order that will work, even with a lot of these automatic deletions set up?) (2) Stop relying on automatic deletions and instead delete children using a loop in a transaction with the parent as the record and the children in a portal? (Inelegant and inefficient.) (3) Use some third way that I don't know about?