Is there a way to specify the order of inserts/updates/deletes used for saving changes across multiple BO's?



Suppose I have multiple tables (Parent, Child, Grandchild) with database-side FK constraints. I might want inserts to be handled top-down (Parent->Child->Grandchild) and deletes bottom-up (Grandchild ->Child->Parent) in order not to violate the FK constraints.



What's the best way to handle this in the general case?

It depends on your scenario.  In most cases, the BusinessLayer/DataLayer will handle this.  There are only a few rare instances where you would have to execute these two updates separately.  In fact, I cannot think of more than one time in all of these years where I had a situation that was complex enough that I had to "hand-code" the delete and inserts separately.  Have you tried this very scenario in your environment?  The BOs and DAL have a ton of logic handling these very types of situations.