web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Merging customers usin...
Microsoft Dynamics GP (Archived)

Merging customers using Customer Combiner and Modifier

(0) ShareShare
ReportReport
Posted on by MartyS7 62

I am using Customer Combiner and Modifier and it is working well.  The issue I have is the invoices that are coming over from the older Customer ID to the new Customer ID appear to change the bill to address on the document.  Is there a way to prevent this form happening and to keep the original information?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Tim Wappat Profile Picture
    Tim Wappat 5,711 on at

    GP has an address book of addresses (RM00102 table). Each address has an index code (address code), unique within that customer.

    I think what you are seeing is the same address code existing in both the source and destination customers, thus the address is getting remapped to the "wrong" address when it is combined.

    Sales documents embed the delivery address in the order header, but have a pointer to this address record in the address book for the other addresses, such as invoice address.

    When you combined the customer, some compromises have to be made to make the process work in a simple manner. You are being caught by such a case.

    As the customers were combined, I'm guessing there was already an address  with the same address code (the index mark) in the destination account. GP does not know what to do so the address from the source customer account was removed and not transferred (or what would you name it?). This has the outcome that the order document from the source is now pointing at the same address id, but the record itself is a different record as it is in the destination account now.

    To solve this, you could use SQL in the pre stored procedure of the combiner to rename any such records that exist in both customers to a new unique name for the source customer, then when it comes over to the new customer it will not clash with the existing ids.  

    If you don't have the in house skills you could engage your partner or independent consultant to design this for you.

    Note: I have not checked this theory out, but have a feeling that this is what has happened.

    Tim.

  • MartyS7 Profile Picture
    MartyS7 62 on at

    Tim,  Thank you.  I will take a look.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans