Failure: Entity-Entity: 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.
This can be a number of thing however, in my case it was attributes that were mapped differently than expected. To resolve it I had to open the Customization XML file and review the mappings there were bring created, comparing then to the CRM instance. By then deleting the inconsistant ones on the tenant the XML file then imported correctly.
Share on Facebook
1) Create the iFrame
Add an Iframe and name it IFRAME_LinkedIn. Uncheck restrict cross-frame scripting box and check the “automatically expand to use available space” box under the row layout section of the formatting tab. Click ok to save the iframe changes.
2) Add Code
Enter the following code on the OnLoad event of the from.
var CRM_FORM_TYPE_CREATE = 1;
var CRM_FORM_TYPE_UPDATE = 2;
switch (crmForm.FormType)
{
case CRM_FORM_TYPE_UPDATE:
crmForm.all.IFRAME_LinkedIn.src=”http://www.linkedin.com/search?search=&company=” + crmForm.all.name.DataValue+ “¤tCompany=currentCompany&searchLocationType=I&countryCode=us&postalCode=” + crmForm.all.address1_postalcode.DataValue+ “&distance=50&sortCriteria=3″;
break;
}
NOTES:
Required Fields
Account Name and Zipcode are required fields for this integration and should be made as required fields in MS-CRM. The Zipcode requirement can be removed by removing the location references in the URL.
Sorting
The lists will be sorted by the default sorting (degrees and Name). This can be changed by changing the sortCriteria value.
1: Number of Connections
2: Degrees and Recommendations
3: Degrees and Name
4: Keyword (CompanyName) relevance
Troubleshooting
If you get a security message when you open the account record or the following message in the LinkedIn iframe “Navigation to the webpage was canceled”, you need to change security settings in Internet Explorer to enable “Display Mixed Content”.
Sourced From Statera
Share on Facebook
Occasionally during testing you need to force the install of CRM and may not be concerned with with the installation pre-checks, the following registry setting will allow the Next buttons to be active although there may be stop issues within the pre-check window. However, I only use this on test environments and would never us this for a production system.
Add the IgnoreChecks registry key to the computer that is running Microsoft Dynamics CRM 4.0 so the installation can proceed when an error is shown in the Environmental Diagnostic Wizard (EDW):
- Click Start, click Run, type regedit, and then click OK.
- In the registry, locate the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
- Right-click MSCRM, point to New, click DWORD Value, and then type IgnoreChecks.
- Double-click IgnoreChecks, and then type 1 in the Value data field.
Share on Facebook
Within MS CRM 4.0 the Lead notes and attachements do not convert to the Account, Contact or Opportunity when converting the Lead. The following is a work around that allows for the information to be mapped to one or all of these entities.
First we will need to customise the account form, adding a new tab and section called Originating Lead Notes and then adding an iFrame called IFRAME_LeadNotes. Set the URL of your iFrame to about:blank and untick Restrict cross-frame scripting.
Next, download and add the JavaScript code to your form onload event:
Publish your changes and you are now able to view the original lead’s notes in your account form.
NOTE: Make sure the OriginatingLead attribute is on the form otherwise the script will error.
To make the solution even more user friendly rather than show a blank iFrame you may want hide the Lead Notes tab if there is no Originating Lead. This solution can also be used in other areas where you want to show notes from another record on a form. The skies are the limit 
Sources From CRM in the Real World
Share on Facebook
- Use Microsoft SQL Server Management Studio.
- Open the table SavedQueryBase in the CRM database.
- Find the query you want to change.
- Set the value of IsCustomizable to “True”.
- Open CRM and go to Customization.
- Open the QuickFind view for the entity you’ve changed the setting. You now have the possibility to edit the filter of the QuickFind view.
- Delete the row “Status = Active”.
That’s it, QuickFind will now search all records including inactive records.
Note: This last option also gives you the possibility to make other non-customizable views customizable.
Sourced From Delta-N
Share on Facebook
Record Counter
When you open CRM and select a view that contains more records than can be shown on one page, you don’t know how many records are in this view. My Record Counter creates a ‘dummy’ record (just emulates it without creation of this record in CRM) and it shows the count of records and pages in the primary field. It works even if the count of records in fetch response is greater then 5000.
Every time this plugin is called, it calculates the count of records and pages.
Sourced From CRM Team Blog
Share on Facebook
Formally you could find the MSCRM linense key in the License table of YOUR_MSCRM database, however with 4.0 this has been moved, you can use a SQL query to retrieve you MSCRM 4.0 license key. To find it, run the following query on the MSCRM_CONFIG database.
select LicenseKey from ConfigSettings
Share on Facebook
http://support.microsoft.com/default.aspx?scid=kb;en-US;2003564
Redeploying large databases can take a lot of time, I generally estimate 1 hour per gig of database size which has turned out to be a reasonable number. For example the most recent redeployment was 10 gig and took between 9 and 12 hours over the course of 3 re-deployments for testing and otherwise. However, with the larger databases you can run into server limitation which has resulted in KB 2003564. Its important to note that once the database has been redeployed some of the settings within the KB will need to be reversed, this is outlined within the article.
KB 2003564 Description
When you import a Microsoft Dynamics CRM 4.0 organization, you may experience a timeout or a hang in the MMC console window hosting the Microsoft Dynamics CRM Deployment Manager.
The Microsoft CRM Deployment Manager window may show up as a white screen during this time and Windows Task Manager will show the program “Deployment Manager” as “Not Responding”. This may even happen if you have increased the OLEDBTimeout setting for Microsoft Dynamics CRM 4.0 to a value greater than when the error was experienced.
If you enable platform tracing, using the steps in KB 907490, How to enable tracing in Microsoft Dynamics CRM, http://support.microsoft.com/default.aspx?scid=kb;EN-US;907490 , you will see an error like the following in the platform trace files (Note that the default log for Importing an organization will be located by default in the %appdata%\Microsoft\MSCRM\Logs\Import.log file for the user who installed Microsoft Dynamics CRM 4.0.
Share on Facebook
