Power BI – Tip for Completely hiding hover text

In our last engagement we had a requirement to completely hide the hover text in a Power BI report.

In Power BI, we can disable the hover text by setting the Tool-tip property to No.

Mentioned below screenshot shows how the hover text looks with Tool-Tip property set to “Yes”. Please note that most of the data / columns in the report have been deliberately hidden.

If we mark the Tool-tip as “Off”, we get the following result

Review that even though we don’t get a Tool-tip with the values in different fields, we still get a hover text on the control.

If we want to completely remove the hover text as well, we can do it by following the mentioned below steps

a) Set the Tool-tip property back to “Yes”.

b) Set the transparency to 100%.

Save the report. Now when a user tries to hover over, there wont be any tool-tip present.

Advertisements

Use Color Codes from Option Sets in both Dynamics 365 charts and Power BI

A really good blog which we can use to control the chart colors in Power BI based upon the option set color codes configured in Dynamics. 

Using the blog, we can set the color each record will occupy in a table view in Power BI based upon the value in its corresponding option set field.

crm chart guy

Option Sets in Dynamics 365 has a setting for each value to specify a color code. This color code is used in the new Unified Interface in the entity specific dashboards. This is a welcome addition as it makes it more easy to persist colors to a specific value and have it be consistent throughout the charts and visuals.

With the August 2018 release of the Power BI Desktop client, we can now also do conditional formatting based on a field with a color code in Power BI reports.

Since we can query option sets directly, and get the color code into the Power BI dataset, we can now use the same color scheme more easily between the two solutions. As the option sets are queried, any updates to values, labels, and color codes in the option set, will automatically update on the Power BI side as well.

For querying…

View original post 59 more words

CDS Analytics Dashboard replacing Organisation Insights

Just wanted to share a feature in Power Platform Admin center which is replacing the analytics provided by Organisation Insights Solution. The organisation insights solution has now been deprecated and is being replaced by the CDS Analytics. More information is provided in the following link

https://docs.microsoft.com/en-us/power-platform/admin/analytics-common-data-service

 

Book First Look – 70 483 Programming in C#

Happy to release the first look of the book 70 -483 Programming in C#. Hopeful about the official release of the book in September this year.

Very thankful to my co-author Madhav and the entire team of Packt for there help during the making of this book. Also thanks to all my colleagues in KPMG for supporting me in this endeavour.

Book Review – The Art of CRM

Just wanted to share a book which i think has been written with great insights to everyday problems which we face while working in CRM.

I happened to read the book during last 3-4 weeks and i think its an excellent read. I think the author has really done a great job in explaining the issues / problems / concepts which we encounter daily while working in CRM. There are also some very good case studies which will provide great insights on different CRM implementations. I think the book bonds well for all set of CRM users irrespective of there roles in the projects. I also felt that for any person who is new to CRM would greatly benefit by reading it.

In all I think its an excellent read.

 

Dynamics / Click Dimensions – Tip for handling Potential Data Quality Issues

On many occasions we rely on external ISV’s such as Click Dimensions for marketing any event happening in the organisation from Dynamics.

One issue that we often face is how to ensure data quality of the contacts being created in Dynamics from such ISV’s.

For example in one such instance below, we are using Click Dimensions to capture registrations for a contact in Dynamics.

Now the challenge is, when it comes to mappings,  Organisation is a lookup in Dynamics but in the Web Content , we can only expose it as a free text. This can cause potential data quality issues, as if the name of organisation does not exactly matches the name in Dynamics , it will not link the Contact with the Organisation.

A potential solution would be to create a custom workflow assembly and follow the mentioned below steps

a) On the Web Content add a mandatory field of Organisation Web Site. In the formatting, using Regex expression, section ensure that users enter the web address in a predetermined format. In the below screenshot, we are doing a custom regex to ensure that no relative paths are present in the URL. This helps us in identifying the parent organisation better.

b) Write a custom workflow on create of contact, and do a lookup on the existing organisations present in the system. If we find a match on the web site link the organisation to the registered contact.

c) Finally to keep organisation web site data clean in Dynamics, enable duplication detection rules in Dynamics.

 

 

 

 

Dynamics Portals – Error on Entity Form Multiple Controls Same ID were Found

While configuring the entity form in portal we were getting an error “Error in Creating Control ID, as multiple controls with the same ID were found.

After analysis we found that when a lookup attribute in Dynamics is rendered in portals, there are three separate controls . One for the ID, one for text and one for entity name. For example, if the attribute name in Dynamics is “abcd_entity”, when the control is rendered in portals it will have the mentioned below controls

a) abcd_entity_name – For text part of the lookup attribute

b) abcd_entity_id – For ID part of the lookup attribute

c) abcd_entity_entityname – For entityName of the lookup attribute

In my case the control ID “abcd_entity_name” was conflicting with the name of an existing optionset attribute in Dynamics. This was causing duplicate ID’s in the system and was this causing the error on the portal.

When we recreated the optionset attribute so as to give it a different name, the above error got resolved.