Un-Merge Customers

tarawilliams · March 31, 2022, 12:01am

Is there a way in Moqui to un-merge customers that were accidentally merged? Not sure how it happened, but I need to figure out how to undo it.

jonesde · March 31, 2022, 4:49pm

There is nothing automated to un-merge parties, but in theory much of it can be done. For reference here is the merge service:

github.com

moqui/mantle-usl/blob/master/service/mantle/party/DuplicateServices.xml#L402

    
      
                              out-map="dupOut" out-map-add-to-existing="false"/>
                      <if condition="dupOut?.matchingInfoByPartyId">
                          <iterate list="dupOut.matchingInfoByPartyId.keySet()" entry="dupPartyId">
                              <service-call name="mantle.party.DuplicateServices.merge#Parties"
                                      in-map="[toPartyId:party.partyId, fromPartyId:dupPartyId]"/>
                          </iterate>
                      </if>
                  </iterate>
              </actions>
          </service>
          <service verb="merge" noun="Parties">
              <in-parameters><parameter name="toPartyId" required="true"/><parameter name="fromPartyId" required="true"/></in-parameters>
              <actions>
                  <entity-find-one entity-name="mantle.party.PartyRole" value-field="fromIntRole">
                      <field-map field-name="partyId" from="fromPartyId"/><field-map field-name="roleTypeId" value="OrgInternal"/></entity-find-one>
                  <if condition="fromIntRole"><return message="From Party ${fromPartyId} is an internal organization, cannot merge/disable"/></if>
                  <if condition="toPartyId == fromPartyId"><return message="From Party ID is the same as To, not merging"/></if>
          
          
        <entity-find-one entity-name="mantle.party.Party" value-field="toParty" for-update="true">
                      <field-map field-name="partyId" from="toPartyId"/></entity-find-one>
                  <entity-find-one entity-name="mantle.party.Party" value-field="fromParty" for-update="true">

For data in entities like ContactMech the PartyContactMech for the original party is still there, so it would be a matter of deleting/expiring those from the merge-to party.

For data in entities like OrderPart (customerPartyId, vendorPartyId), Invoice (fromPartyId, toPartyId), etc those party ID fields are audit logged so you can find the old party ID in the EntityAuditLog history and change them back to before the merge.