Archive for January, 2008

Migrating notes and attachments to the Accounts (Data Migration CRM 4.0)

If we follow the data migration help , the attachment would appear in CRM but without any text (0KB).

I will cover it in the following steps and any input will be appreciated if someone encounter this blog.

1 = First , I have a folder on desktop and under that folder , I have CSV file and another subfolder , where I have documents, I wish to attach with an account. The name of subfolder must be “Documents”.



2 =Map the file to the existing entity and choose “Note” and check the “include attachment”.



3 = During the setup of Data migration, related the “Company Name” on CSV file with regarding and then Choose “Account” and the select “name” (or company , whatever it is in your customize system).


4 = Finally we import the attachments .

Advertisements

Multi-tenancy example in Microsoft CRM 4.0

Hosting companies can have many customers by using single installation of Microsoft Dynamic CRM 4.0 Enterprise.
I used single CRM installation for three organizations named –DK, USA, UK and USA as default organziaton. I used deployement manager to add further organizations -DK and UK.
We have one MSCRM_CONFIG database and three databases for three organizations.

Now one can view the url of all three organizations.

Using Status and Status Reason in Data Migration Manager in CRM 4.0

We can use the combination of SateCode and Status Reason for importing the data with different status, like importing accounts as “Inactive”, importing “Email” as history, or importing lead as cancelled.

Lets take example of importing Accounts as “InActive”:

In order to import the Account as “InActive”, Status and StatusReason column must be in source file. The value of Status (1) and StatusReason(2) will import the record as “InActive”.

Importing Email as History :

In order to import the email as history , Activity Status and Status Reason columns should be present in source CSV file. The values of these two columns should be –Activity Status (1) and StatusReason(6) .

Note: Values combination can be obtained from “entity customization” or “from SQL (views).