Per today the whole Masterdata function is one way, so if a record is accidently deleted in the company receiving data then it is not possible to recover this without deleting the entire coupling list for the table and then running a matched based coupling afterwards.

The following would be very helpful and a great improvement to the functionality

1: If a confirm is added after pressing delete on a record that is coupled asking if you also want to delete the coupling, this would give an extra step when deleting and causing less "deleting by accident"

2: To be able to either run a filtered version of the Delete Couplings job or to be able to go into the coupling table to delete the required couplings so that it is possible to restore the data using Masterdata function.

I do believe that the Masterdata MGT function should have the same function as for the Dataverse where it is possible to set up an option regarding Resolving Deletion Conflicts, with this as an option for setup in Masterdata MGT then there would be no need to have either of the above to solve if a record is deleted.