Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

CRM 2016: Customizing the Sales Performance Dashboard (workaround)

Since CRM 2011 the is a Problem with customizing the OOTB Sales Performance Dashboard.
Until today with CRM 2016 SP1 it still is not possible to modifiy the dashboard with the dashboard designer in CRM:

https://support.microsoft.com/de-de/kb/2741768

Even in MS Connect, Microsoft does not pay a lot of attention to this issue, as its not having many votes.

If you try to modify it you will get an error:
"Cannot Edit Dashboard. The dashboard could not be opened. Maximum no. of columns allowed in the layout is 4."
I also tried to make an unmanaged solution of the dashboard with no success. Even with the default solution you will not get out the required formxml that you want to change.

If you have CRM on-prem you still have a chance to actually retrieve the required form XML from the database.

This article helps you to find the right table in the ORG_MSCRM database:
https://msdn.microsoft.com/en-us/library/gg327869.aspx

In this case Need to search through the systemform table. Just search in "Name" column for the right title of the Dashboard. Then copy out the form XML and it should look like this:



Then create an unmanaged solution in CRM and export it with the Sales Performance Dashboard.

Next, unzip the file and open the customization.xml with e.g. Notepad++.

Then search for the Dashboard and it should look like this:



Now we update the XML with the actual form XML and other view things:





Then you can do whatever changes to the form XML to reflect your requirements.

Finally save the file, zip everything together and import it back to CRM and publish it.

Voilá!





Comments

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu

CRM 2016 SP1: Solution import failed with Solution With Id = 12ac16ec-41d5-1685-a230-0b1c31499250 Does Not Exist

Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise. Ronald Lemmon already posted the same issue on his blog: http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html I expected it to be fixed with SP1 but it is still happening every now and then. With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore. select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID' Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated. What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system. To find out the id of