Does the order of the fields for the entities matter when importing
customizations? We noticed that the order of fields for the contactbase in
our live system is different than the test system.
When importing the customisations from the live system we get an error
message:
'The attribute map is invalid. The selected attributes should be of the
same type. The length of the target attribute should be equal or greater than
the length of the source attribute and the formats should match. The target
attribute should not be used in another mapping.'
Any help would be really appreciated.
Thanks,

The order of the fields shouldn't make any difference. One possible cause of
your problem is if you are only importing certain entities in one go, and one
of them maps to fields in another entity that has yet to be imported. This
can be resolved by exporting all entities, them importing them all in one go.

Alternatively you may have some corrupt mappings. This can occur (especially
on systems upgraded from CRM 1.2) without otherwise affecting CRM.

What I do to resolve this is selectively edit the <EntityMap> elements out
of the customization file (having made backup copies of the file)

"Dev" wrote:

unfortunately, it could be just about anything. Best bet is to enable a CRM
platform trace before you import the schema. when it dies, review the trace
files for exceptions, and you can usually tell from the last action it was
performing before it died, what the problematic field is.

MBS Support is also well versed at troubleshooting these

Dave


"Dev" <Dev@discussions.microsoft.com> wrote in message
news:87B521BA-E58C-471C-AE29-1A973ADBDDFD@microsoft.com...