Data Migration Manager: Advanced Transformation Mappings

Airline Travel » Data Migration Manager: Advanced Transformation Mappings

Airline Travel » Data Migration Manager: Advanced Transformation Mappings — Mon, 24 Mar 2008 22:10:32 GMT

PingBack from http://www.travel-hilarity.com/airline_travel/?p=2199

re: Data Migration Manager: Advanced Transformation Mappings

ceo_uk — Tue, 25 Mar 2008 21:25:06 GMT

It's a nice post. I wonder how did you build this query?

Cheers,

Jim

re: Data Migration Manager: Advanced Transformation Mappings

Jeff Wessling — Wed, 26 Mar 2008 01:49:36 GMT

I've enjoyed the flexibility allowed with the Data Migration Manager's transformations, however I've run into an issue where I get a 'Conversion Error' screen with no exported errors when I try to execute the 'Replace' transformation on a source data field that is more than 500 characters long. Is this a hard limitation or can this be configured somewhere?

Any help here is appreciated, I haven't found anything on this anywhere else.

Thanks,

Jeff

re: Data Migration Manager: Advanced Transformation Mappings

Abhishek Agarwal — Thu, 27 Mar 2008 19:22:47 GMT

Jeff,

This seems to be a bug. Please get in touch with the SE team for a hotfix request. As a workaround, you can have a data with a max length of 500.

Thanks

Abhishek

Data Migration Manager: Advanced Transformations

Microsoft Dynamics CRM Team Blog — Fri, 04 Apr 2008 18:17:28 GMT

Advanced transformations used in Microsoft CRM Data Migration Manager is a powerful and efficient technique

re: Data Migration Manager: Advanced Transformation Mappings

Shaunn — Tue, 08 Jul 2008 21:06:35 GMT

Nice post. Would it be possibly to go over an example of M:N mappings. This is something I've been curious of.

Thanks.

re: Data Migration Manager: Advanced Transformation Mappings

Simon — Wed, 25 Feb 2009 05:38:31 GMT

can anyone tell me how to import the "Annotations" table from CRM 3.0 to 4.0 using this utility (Upgrade is out of the question)?

Without getting the "Row is too long to import" message.

csv files are NOT always a good transport media for data, they have limitations.

Version 3.0 migration utility was lightyears ahead of this one in so many ways.

Undocumented Features

Simon — Thu, 26 Feb 2009 06:10:16 GMT

Better hope your csv files don't have too much data in them, there is a specific size limitation to these type of files which can be uploaded.

What that limitation is I have no idea, it's not mentioned in the error message nor the documentation.

NOTE 1: The width limitation is 65000 chars, if any row exceeds this you will not be uploading any records from that file. (This includes mime encrypted files like PDF files stored in Note fields eg. Annotations Table)

NOTE 2: Any memo fields will have to be re-formatted to remove carrage return and line feed characters. Not a bad idea to remove any commas, quotes and any other un-printable chars as well. This is so that the file can be recognised as a valid CSV file.

The version the migration utility for CRM 3.0 did not have any of these limitations.