When you attempted to create new contact party records( Associated contact) under the account record these newly created contact party records were incorrectly associated with a different account but with the same party ID, which basically by design behavior as the plugin step `Microsoft.Dynamics.GABExtended.Plugins.AssociateContactForParty` is part of the dual-write Party and Global Address Book (GAB) solution, which manages the association of contacts to parties (accounts, contacts, vendors) between Finance and Operations (FnO) and Customer Engagement (CE) systems. when adding a new contact for party record, the plugin links the contact to any prospect that has the same party ID, which causing conflicts, please consider changing this behavior.
Comments
One of our customers has shared with us the work around they have used to link the correct account as bellow:add an extra field 'associated account to the contact for party tablevia javascript, fill the original associated account field with the value that was entered in the new fieldsave the record (MS plugin will update the associated account to another accountadd a power automate flow that will compare the new associated account and the original associated account - and update the original associated account with the value of the new associated account. that way we would always update the field to the value entered by the user - and avoid the problem that is created.
Category: Account, Contact, Calendar and Activity Management