Holger,
I agree that if you choose to do this manually, you should be a detective.
However, if you could just extend the "Rename" functionality, this could be
done easily.
I also agree that financial transactions may not be altered when posted.
However, as I see it you actually change the records even with a simple
"Rename".
I would not want to do this on database level only, since this would be a
source of errors. I spoke to a MBS project manager recently about this
issue, and the functionality of merging/joining two customers has actually
been on the to-do list for a long time. Unfortunately, the functionality has
been stripped from the various updates due to last minute changes - just as
in real life ... :-)
Given the fact that MBS has considered the functionality, I would suspect
that we are indeed allowed to merge customers; probably with some sort of
logging and/or auditing mechanism.
You have made me think twice ... :-)
/Jens
-----Oprindelig meddelelse-----
Fra: Holger K. Pedersen [mailto:[EMAIL PROTECTED]
Sendt: 17. november 2004 22:56
Til: [EMAIL PROTECTED]
Emne: RE: [development-axapta] Joining two customers into one
Making the change of all fields referencing the Account is fairly easy,
seen
from the database point of view, but the business processes triggered by
changes must also be complied. This is a detectives work to figure out.
This
is probably the reason you can't do what you want, since nobody has spent
the time to make it work. It would cost a fortune to do it completely.
The financial transactions are not allowed to change when posted. The same
considderations might apply to other tables as well.
You can fake the data, going to the database level, doing some UPDATEs on
the rows referencing the given AccountNum, but you should make sure, the
row
is not used by other tables in the whole database.
I don't think you should try to do it, unless you know exactly what
consequences it has.
I hope this makes you think twice... :o)
>From: "Jens Strandberg" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "[EMAIL PROTECTED] Com (E-mail)"
><[EMAIL PROTECTED]>
>Subject: [development-axapta] Joining two customers into one
>Date: Wed, 17 Nov 2004 21:18:28 +0100
>
>
>
>As you probably know standard Axapta does not allow you to join two
>customer
>(or supplier) records; i.e. if you have added customer A and later on by
>mistake added the same information as customer P, you cannot combine
these
>two - moving all related records from customer P to customer A.
>
>The only option you have is to change the primary key for a given
customer,
>which is not very useful in this case.
>
>As I see it, the only way to join two customers into one is to develop
some
>piece of code that would do the trick for you.
>
>Now, it would be easy to create such a script, if we could just see how
the
>changing of the primary key is done. However, this is hidden well inside
>Axapta.
>
>I was wondering if any of you guys would have some ideas and pointers to
>this issue. Also, if you happen to know a solution to solve this, this
>would
>be very interesting piece of information.
>
>Thanks in advance.
>
>/Jens
>
>
>
>
Yahoo! Groups Sponsor
ADVERTISEMENT
----------------------------------------------------------------------------
--
Yahoo! Groups Links
a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
b.. To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
