Share
Report
1,761In responding to a recent post on merging customers, I found that AX 2012 R3 now has the ability to "Merge Customers".
I did some preliminary testing and it appeared that the merge process did that - Merge customers. I found that when I merged a customer, I was notified that ..."All records with Customer A will now be associated with Customer B".
Awesome. That is exactly what I was looking for. Having previously worked with Dynamics GP, I think I was expecting similar treatment as to how a customer would be merged. In GP - when you merge a customer, that customer and all records (open transactions and history) are converted to have the destination customer's ID associated with it.
After I merged a customer IN AX, I attempted to create a Sales Order and an Invoice with the old customer ID, but was notified that the customer selected had been merged with Customer B". In selecting "OK" to that message, the customer added to my transaction was Customer B. Good, So I can no longer transact against Customer A.
However...Customer A still exists with its history and Open Transactions. On a go forward, I cannot create new sales transactions against Customer A, but it appears that I can still transact other transactions against Customer A.
So, I would state...I do not know for certain what Microsoft means by "Merge" on the customer beyond preventing new transactions and redirecting attempts to transact with old customer to the new customer.
Can anyone add to this dialogue? What can you and what can you not do once you have performed a merge on a customer? I would really like to find out what "All records with Customer A will now be associated with Customer B" means in regards to past and future transactions and ability to use Customer A.
Thanks. This should be interesting...
*This post is locked for comments
All responses (
Answers (
