Sunday, February 05, 2012

Categories

Archive

Tag Cloud

Recent Comments

"FYI - This does not work with "set-psdebug -strict". This setting requires all variables be defined before they can be referenced, the equivalent of "option explicit" from vbscript. " Read more
by Bill Faulk on Export CRM customizations using PowerShell

"Hi Molly -- this kind of stuff can be dicey to troubleshoot. Make sure the workflow scope is set to Organization and not User and that it is published. Sharing is not required. Then make sure their role can execute workflows. Hope this helps, Phil" Read more
by Phil Edry on Allow Multiple Users to Sync the Same Contact to Outlook Effortlessly with Microsoft CRM

"Phil, I spoke too soon. I was able to get everything set up. I was testing this with out inside sales group and when they try to run the workflow they receive an error saying they do not have permission to run the workflow. I went back and made sure they had rights to the sync entity and the workflow. I shared the workflow with them (I believe that is what I should do), but they still cannot run it. What else could I be missing? Thanks in advance. Molly" Read more
by Molly McGill on Allow Multiple Users to Sync the Same Contact to Outlook Effortlessly with Microsoft CRM

"Glad I could help!" Read more
by Phil Edry on Allow Multiple Users to Sync the Same Contact to Outlook Effortlessly with Microsoft CRM

"Thanks Phil! That worked. I knew it was something simple that I was just overlooking." Read more
by Molly McGill on Allow Multiple Users to Sync the Same Contact to Outlook Effortlessly with Microsoft CRM

"Hi Molly -- open a role that the salesman has and click on the very last tab "Custom Entities". Make sure he has rights on the Sync User entity. Best, Phil" Read more
by Phil Edry on Allow Multiple Users to Sync the Same Contact to Outlook Effortlessly with Microsoft CRM

"I think this is really going to help us. I am having a problem configuring outlook for one of our salesman and I cannot get "Sync Users (contact)" to even show up. I'm sure I'm missing something in their role. Do you know what should be changed to allow them to see that?" Read more
by Molly McGill on Allow Multiple Users to Sync the Same Contact to Outlook Effortlessly with Microsoft CRM

"hi, good staff.I think calender is the most important aspects of any crm solution.It help to update the information about the events and also helpful to for modification of transactions and easily approachable medium " Read more
by real estate crm on Adding a Custom Calendar to the CRM UI

Altriva Team Blog

Importing Customizations from one CRM Online Instance to Another CRM Online Instance

Posted by: Phil Edry on 12/11/2009
  • Categories:
  • CRM

One issue we’ve run into with two of our Microsoft Dynamics CRM 4.0 Online customers pertains to importing their customizations into a new CRM Online instance. The error you receive when you attempt to import the customizations is “Failure: lead-contact: This attribute map is invalid. A valid attribute map must meet these requirements: - The data type must match. - The length of the target attribute cannot be shorter than the source attribute. - The format should match. - The target attribute must not be used in another mapping. - The source attribute must be visible on the entity form. - The target attribute must be a field a user can enter data into. - Address ID values cannot be mapped.”

To resolve this issue, you can either figure out which of the requirements in the error message are causing the problem, or if you’re in a hurry, you can remove the XML pertaining to mapping leads to contacts and accounts. WARNING: This may break your mappings from leads to contacts and accounts if you’re not careful. This is also an unsupported route to fixing this issue.

To remove the XML pertaining to mapping leads, open the zip file with your exported customizations and then extract the customizations.xml file. Open it in your favorite XML editor and do a search on the text “<EntitySource>lead</EntitySource>”. This will be the first XML element after an “<EntityMap>” element. If “<EntitySource>lead</EntitySource>” is immediately followed by “<EntitySource>contact</EntitySource>”, then you know that this “<EntityMap>” maps leads to contacts. Very carefully delete starting at “<EntityMap>” and ending at the very next “</EntityMap>”. Try the import again. If you get a similar error for accounts instead of contacts, then remove the “<EntityMap>” for lead to account as well.

The import will now succeed, but there import window may become frozen at 100% complete. If this occurs, wait a few minutes, then close the import window and publish all customizations. Test creating a lead, and then creating a contact and account from that lead to make sure nothing is broken.

-Phil Edry

Create a trackback from your own site.

1 Comment

    • Feb 05 2010, 4:30 PM Gretchen Mann
    • Thanks! I encountered this same error, so this was helpful. It would be nice to know what attributes are causing the problem. I heard that some rollups actually changed the size of some attributes. I'm not sure how that would be related to CRM Online or if it could be impacted by the date the organization started using CRM.

Leave A Comment



Please enter the CAPTCHA phrase above.



Copyright 2010 by Altriva LLC