Good Morning

I am currently doing some tests regarding MSCRM data migration. I have a
small question regarding population of the CDF database with the legacy
data.

As I understand it, if fields have been added in the MSCRM configuration,
then when you populate records in the CDF_<entity> table, then a
corresponding record is added to CDF_<entity>_ext table. I then have to
populate the ext table with the legacy data required to go into the
additional fields.

I have been using the SQL data import wizard which works great for the
CDF_<entity> table, but I am concerned about how I will marry up the
extension data with the correct record when I populate the CDF_<entity>_ext
table.

Is there something that I am missing, or is it a two stage process as I
described?

Any help would be appreciated.

Regards

Peter Cutts

Thanks, Kevin

Does this mean that rather than just 'dumping' the legacy data into the ext
table I will have to do some sort of look up on the ext table before each
extension record is added so as to append it to the trigger created record
that has the correct ID?....(I hope that makes sense!)

Pete

"Kevin @ 3NF" <Kevin@dallasdbas.com> wrote in message
news:usftdehRDHA.1804@TK2MSFTNGP11.phx.gbl...

Not sure I followed that....

Lets say you have a legacy datafile with 4 colums:
AccountID
StandardCol1
StandardCol2
CustomCol4

You would run a DTS task to move the first three columns into the
CDF_Account table, and another to move columns 1 and 4 into the
CDF_Account_ext table.

The migration tool should hook those two tables together when it runs. This
relationship is a one-to-one....

I have not tested this at all, so your mileage may vary...

Kevin
"Peter Cutts" <peter.cutts@DELETEquixote-uk.com> wrote in message
news:%23q31snhRDHA.2332@TK2MSFTNGP10.phx.gbl...

Kevin

Thanks. I understand your logic and this would work fine if not for the
triggers on the entity table.

The Data migration guide states that you should first populate the entity
table. Each time you create a record in this table a record is created,
storing the standard fields and a trigger is fired to automatically create a
record in the ext table. The next stage is to put the custom data in the
ext table.

Because a basic record has already been created in the ext table by the
trigger, my problem is in matching the correct legacy data with the correct
record in the ext table. You are in effect updating a system generated
record rather than inserting one.

Am I making sense?....in your example,you first populate the entity table
with AccountID, StandardCol1 and StandardCol2. When this record is created
a trigger creates a corresponding record in the ext table. Now here is my
problem: How do I update that newly created record in the ext table with my
CustomCol4 data?

I really appreciate your time on this with me, Kevin....and is there anyone
else out there that has overcome this problem.


Peter


"Kevin3NF" <Kevin@DallasDBAs.com> wrote in message
news:%23ReougkRDHA.1072@TK2MSFTNGP10.phx.gbl...

Must have missed that in the documentation, as I was not dealing with any
custom fields in the import I did recently. Sounds like it may be worth a
$65 call to MBS....

If my test system was customized, I would just give it a whirl for you but
alas...it is set up plain vanilla so my clients can see what MS CRM looks
like out of the box.

--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm



"Peter Cutts" <peter.cutts@DELETEquixote-uk.com> wrote in message
news:#kO0NysRDHA.3192@TK2MSFTNGP10.phx.gbl...

Peter,

You have a few options here:

- DTS the custom data into another table and then write an update statement
- Delete the rows from the ext table created by thge trigger
- Delete the trigger

Obviously if you go one of the last 2 routes, you need to make sure all rows
are accounted for in the ext table of the app will rpobably bomb.

"Peter Cutts" <peter.cutts@DELETEquixote-uk.com> wrote in message
news:%23kO0NysRDHA.3192@TK2MSFTNGP10.phx.gbl...
Kevin

Thanks. I understand your logic and this would work fine if not for the
triggers on the entity table.

The Data migration guide states that you should first populate the entity
table. Each time you create a record in this table a record is created,
storing the standard fields and a trigger is fired to automatically create a
record in the ext table. The next stage is to put the custom data in the
ext table.

Because a basic record has already been created in the ext table by the
trigger, my problem is in matching the correct legacy data with the correct
record in the ext table. You are in effect updating a system generated
record rather than inserting one.

Am I making sense?....in your example,you first populate the entity table
with AccountID, StandardCol1 and StandardCol2. When this record is created
a trigger creates a corresponding record in the ext table. Now here is my
problem: How do I update that newly created record in the ext table with my
CustomCol4 data?

I really appreciate your time on this with me, Kevin....and is there anyone
else out there that has overcome this problem.


Peter


"Kevin3NF" <Kevin@DallasDBAs.com> wrote in message
news:%23ReougkRDHA.1072@TK2MSFTNGP10.phx.gbl...

Thanks Matt,

I think that I may well try deleting the rows created in the ext table and
DTS the custom data into it directly. I am assuming, of course that I can
get the primary keys to correlate with the entity table!...but what the
hell - I am only doing some test runs and sometimes we only learn from
mistakes ................(don't we?!!!)

Thanks for the input.

Regards

Peter


"Matt Parks" <Matt.Parks@removetoX_XRevereGroup.Com> wrote in message
news:uDZ2NYvRDHA.3700@tk2msftngp13.phx.gbl...

Rick

Thanks - I think that pretty well completely clears up the fog that I had
about this one! - should be able to give this a spin now.

Your help is much appreciated.

Peter

"Rick" <gambler@sva-dot-com> wrote in message
news:027d01c34a2c$fca58bf0$a101280a@phx.gbl...