Dynamics Biz Apps Blog

NOTE: This process works in 2011 or 4.0, the following screen shots are form a 4.0 system.

MS CRM does not give you the ability to, in a straightforward manner, convert Leads in bulk. The widespread knowledge is that you have to convert them one by one. However, there is a workaround…

This would be through Marketing Lists – it’s a way to exploit the features of the Marketing Lists functionality, without using the Marketing Lists to “market” per se. And there’s another plus – no plug-ins or custom development work required!
Create a new Marketing List called “Bulk Disqualify” or something; you can reuse it if this comes up later, so it’s good to know what it was used for. Set it to use Leads as the Member Type.

Add all the Leads to the Marketing List (you can do this in bulk on the toolbar, or individually). You go to More Actions (or just Actions from inside of a record), and then click Add to Marketing List.

Once you have all the Leads in the list, you can highlight them all, then click More Actions, and then click Convert Lead. It will then allow you to qualify……

…….or disqualify each of the records selected at once.

NOTE: If you have more than one page of Leads in the Marketing List, you will probably have to do the conversion process more than once (but it beats doing it 200 times!). I would do the first page entirely – then click to view the next page. Follow those steps until you have all of them disqualified. It may allow you to do all of them at once, but you’ll have to see.

Sourced From: Dynamics Care

Share on Facebook

Exception message: The base class includes the field ‘reportViewer’, but its type (Microsoft.Reporting.WebForms.ReportViewer) is not compatible with the type of control (Microsoft.Reporting.WebForms.ReportViewer).

1. Download and install Microsoft Report Viewer Redistributable 2008. http://207.46.19.190/downloads/details.aspx?FamilyID=cc96c246-61e5-4d9e-bb5f-416d75a1b9ef&displaylang=en

2. Search and replace within the web.config Microsoft.ReportViewer.WebForms, Version=8.0.0.0 to 9.0.0.0

3. Do an issreset following the changes

This corrected the reports.

Share on Facebook

 http://support.microsoft.com/kb/914921

Within CRM 4.0 and 2011 you cannot access the field mappings area for the Invoice Product, Order Product, Opportunity Product, and Quote Product entities in the Microsoft Dynamics CRM UI. To map between these entities you must query the sql database for the specific relationship GUID’s. 

In Sql run the following Query:

select SourceEntityName, TargetEntityName, EntityMapId from EntityMapBase where SourceEntityName in (‘opportunityproduct’, ‘quotedetail’, ’salesorderdetail’) and TargetEntityName in (‘quotedetail’, ’salesorderdetail’, ‘invoicedetail’);

With the appropriate result place the GUID in the following URL, setting the server:port and organiziontion appropriatly.

 http://crm:5555/Contoso/Tools/SystemCustomization/Relationships/Mappings/mappingList.aspx?mappingId={GUID}

This will return a UI that will allow you to add the desired mappings.

Share on Facebook

I am seeing more and more clients with Rollups installed but not having done the manual changes following the installation. Customer Effective has a great article on this and I believe is worth publishing here.

_____________________________________________________________

You are probably aware that approximately every 8 weeks Microsoft releases an Update Rollup, a cumulative set of updates and fixes.

When deploying an Update Rollup, it’s important to realize that update rollups include two categories of updates:

1. Bug fixes—these are fixes to issues where CRM is not working as designed, and they are applied automatically when you install the update rollup.

2. Design changes—these are updates where CRM is working by design, but Microsoft has made a change in the way CRM works. For example, there were recently some updates that changed how CRM handles housekeeping of completed system jobs. Design changes require a manual change on the CRM server, typically a registry change, to enable the update, since Microsoft doesn’t want to change the system design for users who expect it to work the way it was originally designed.

The changes that require a registry change to enable are included in knowledge base article for the update rollup under the section “Hotfixes and updates that you have to enable or configure manually.”

This is why it’s important to read the knowledge base articles associated with CRM update rollups before you roll them out. Read through the changes included. I only make the changes that require registry changes if the fix addresses an issue that I’m seeing in my environment. Making changes that fix issues that you are not experiencing can have unintended side effects. It’s ok to pick and choose which ones you enable.

This is also why, if you read a blog or hear somebody from Microsoft say “Rollup X fixes that problem,” don’t automatically assume that the problem is fixed because you have installed the update. Read the small print—there may be additional steps required to enable the change.

Sourced From: Customer Effective

Share on Facebook