What you suggest might work fine for now. However, I had a lot of trouble when I tried to upgrade an environment from 4.0 to AX 2009 where demo data had been loaded into the DAT company. Even trying to run the DatabaseTransDelete and deleting records in master records did not resolve my difficulties. There are so very many tables into which data had been loaded - I could not find them all. I could not do the post Synchronize steps for the upgrade. I got all kinds of errors that I just could not resolve.
If I were you, I would create a clean installation -- export all 20 companies and import them into the clean company. Export DAT company and import to the new company. Ultimately, that is what I did to be able to do data upgrade. I exported the desired companies, imported them into a clean 4.0 upgrade never touching the DAT company. Finally then, I was able to get through the data upgrade successfully. I know that sounds terribly painful. Perhaps you will not have problems until it is time to upgrade to a new release. But you asked for us to let you know about the "challenges". Mary Ann On Mon, Mar 2, 2009 at 2:41 AM, Jens Strandberg <j...@strandbergs.dk> wrote: > Hello there, > > Our Ax application (Ax3SP4) holds 20 different company accounts. During the > initial installation the data for the first company was placed in DAT, while > all subsequent companies were placed in separate accounts, eg. ABC, DEF etc. > > Now, I would like to copy DAT onto another company account, let's say XYZ. > This can - as you know - be achieved using default Ax functionality. After > this I would do a DatabaseTransDelete in DAT followed by some home-made > utility that would delete master information like items etc. > > Afterwards, all users should have their profile point to account XYZ > instead, and we should be home free... at least in theory. > > But - I was wondering if any of you guys could see any challenges in this > approach, since the DAT company account is also used to hold other, non > per-user tables and features like users, access etc. > > Any pointers or experience shared will be much appreciated. > > Thanks. > > /Jens > >
