If dual write is enabled and you utilize the "change party association" functionality within Finance and Operations and change the party from an "organization type" party to a "person type" party, data corruption occurs within the Dataverse.

Expected behaviour:

After changing the party association, the "Account" record in Dataverse should be disabled or deleted. A new "Contact" record should be created to represent the new person-type customer. Consideration needs to be made about how the existing linked content in Dataverse is handled - if there's existing cases, etc. we'd likely need those migrated to the new association!

Actual behaviour:

The "Account" record representing the customer as an organization remains intact. This record cannot be edited or deleted - a dual write exception is encountered.