- Migrating from pilot to new CRM
- Posted by Chris on April 5th, 2004
Hey there,
in the middle of migrating my data from a pilot install of
CRM to the production version. Had to re-install as had
the MSDN version for the pilot, and am now migrating my
data across. Although have GUID mapped all old - new
Users, Territories, Business Units I can't see any data
through the web client?
Can obviously run the queries directly on the database,
and ran a trace in which the same commands used when on
the web client return with no records, while when running
the same on Query analyser show results???/
can anyone help?
- Posted by Chris Ward on April 5th, 2004
Well just to add further to my own question... I re-booted
the front-end and now I can log in via my own User ... but
still cannot see anything under the Admin user. I assume
that if I can log in under my own user, then this will be
the same for all the other users I have specified, but
still not the admin user????
- Posted by Matt Parks on April 5th, 2004
Chris,
How exactly are you migrating the data? There is a lot more to the CRM security
than the GUIDs used for the FK's. It is recommended that you use the Data
Migration Framework to populate the CRM database or write your own process using
the SDK.
Matt Parks
----------------------------------------
----------------------------------------
On Mon, 5 Apr 2004 01:23:43 -0700, "Chris Ward"
<anonymous@discussions.microsoft.com> wrote:
Well just to add further to my own question... I re-booted
the front-end and now I can log in via my own User ... but
still cannot see anything under the Admin user. I assume
that if I can log in under my own user, then this will be
the same for all the other users I have specified, but
still not the admin user????
- Posted by Chris on April 6th, 2004
Matt,
Used the DMF to populate the new CRM database .. and only
had a few customisations to the Sales portion of CRM.
Looking at the Migration framework .. it's not as if it
gives you anything specific and fantastic over just
shoving the data in there yourself using SQL. You still
have to use Bulk Inserts and DTS, and hence I just went
through most of my tables and mapped old -- new GUIDS for
Territory id, SystemuserId and BusinessUnitID (and
OrganisationID).
All migrated across with no errors and hence the fresh
install included with new AD objects now works fine.
Although it is only this Admin user that is affected. And
from what I can tell. All freshly created objects appear
under the Creator Ownner and now the Admin user aswell.
Chris.
- Posted by Matt Parks on April 6th, 2004
But there is embedded security information in some of the binary fields that
wouldn't have been updated properly. Using the DMF would have updated these
fields to be in synch with the new installation. I'm not saying it can't be
done, only that it takes a lof of effort to get everything working properly.
Using the DMF eliminates the need for that effort.
It's not surprising that newly created records appear properly, as they were
created using the app and thus would have had the security info set properly.
Matt Parks
----------------------------------------
----------------------------------------
On Mon, 5 Apr 2004 16:44:14 -0700, "Chris" <anonymous@discussions.microsoft.com>
wrote:
Matt,
Used the DMF to populate the new CRM database .. and only
had a few customisations to the Sales portion of CRM.
Looking at the Migration framework .. it's not as if it
gives you anything specific and fantastic over just
shoving the data in there yourself using SQL. You still
have to use Bulk Inserts and DTS, and hence I just went
through most of my tables and mapped old -- new GUIDS for
Territory id, SystemuserId and BusinessUnitID (and
OrganisationID).
All migrated across with no errors and hence the fresh
install included with new AD objects now works fine.
Although it is only this Admin user that is affected. And
from what I can tell. All freshly created objects appear
under the Creator Ownner and now the Admin user aswell.
Chris.
