Introduction: Once a User exports a report to Microsoft Excel from a Microsoft Dynamics CRM environment, they may want to further filter the report in Microsoft Excel. Issue: An issue I came across recently was that the report, when exported to Excel, would not allow me to filter in Excel for the first few columns, as shown in the screenshot below. On further testing, I found that this was due to the Title text box above the table. Solution: Once the side of the text box was extended to the very end of the report (as shown above), near the end of the page, Excel allowed the filters to be applied to all columns in the exported SSRS report. That solves it!

Introduction: In this article, we will learn how to set a default dashboard when you login to Power BI Service. Default Dashboard is termed as ‘Featured Dashboard’ in Power BI. Steps for configuring featured dashboard: Login to Power BI Service Open the Dashboard you need to display when you open Power BI Service. Click ‘Set as featured’ on the top navigation bar of your dashboard. A Pop-up window will appear for confirmation. Click on ‘Set as featured dashboard’ button. 1

Introduction: Recently, we encountered an issue while exporting the SSRS Reports to Excel. In CRM, the SSRS Report was displaying the data correctly but for few filter criteria, we were not able to export the Reports to Excel.  On troubleshooting in SQL Data Tools, we found that it was throwing the below error. Error Details: The row item structure object corresponding to a line cannot be null. Reason for the error: We had 2 matrix in our Report one of which had data and another was retrieving no rows according to few criteria. Whenever a matrix is null, you cannot export the Report to Excel as Excel does not render null matrix. Solution: Add a visibility condition on the matrix that if the dataset pertaining to the matrix returns no rows then hide the table. Voila! You are good to go. Happy Reporting!!

Introduction The September 2018 Update of Power BI has finally brought to users, the functionality to copy data from a table or matrix in a report. This has been a much-requested feature as one often finds themselves needing to copy a value or columns of data from a report with no option to do so. Steps: Now, if you want to copy a value, several columns  in a table or matrix you can do so by following the steps below: Copying one value :  Select the value->right-click on the selection -> select ‘Copy Value’ -> An unformatted value will now be added to your clipboard. Copying several columns of data: Select all the data in the required columns->right click on the selection and select ‘Copy Selection’.-> The required data and column headers are copied to the clipboard. In a Matrix, when you select one value->right-click-> ‘Copy Selection’-> All measures required are copied along with the value ( as shown in the screenshot below). Conclusion: This is a long-awaited feature of Power BI and will definitely enhance user experience while navigating and using Power BI reports.

Problem: There is no in-built function in SSRS where we can count the number of Saturdays and Sundays between any two dates in SSRS. This is a needed function for scenarios where we only need to get a count of working days.’ Solution: Following is a formula that can be used for getting an accurate count of weekends. = (((DateDiff (DateInterval.Day, DateAdd(DateInterval.Day,7-WeekDay(Parameters!startDate.Value),Parameters!startDate.Value), DateAdd(DateInterval.Day,7-WeekDay(Parameters!endDate.Value),Parameters!endDate.Value).AddDays(1)) + 1)/ 7)*2) + iif(weekday(Parameters!endDate.Value)=7,1,0) + iif(weekday(Parameters!startDate.Value)=1,1,0) -1 Here instead of Parameters!startDate.Value and Parameters!endDate.Value, you can use any other Start Date or End Date.

Microsoft Power Bi enables you to find and visualize data, share your findings and collaborate in the modern ways in the form of reports and dashboards. In short, it is a collection of online services and features to enhance your business. Power bi support allows you to migrate huge data from various sites into power bi desktop using the integration process. You can easily edit the data or you can also plan to edit it later after you have imported it on your desktop. Power bi helps you to overcome all your business problems with ease making you stay up-to-date with all necessary and relevant information that is of utmost value for you. The team of experts involved have a huge experience in working with all kinds of businesses across the world. Introduction: Row-level security (RLS) with Power BI can be used to restrict data access for given users. Filters restrict data access at the row level, and you can define filters within roles. Steps: To create on a Power BI Solution, you will start by going to the Modellingribbon and then select Manage Roles. This will launch the Manage roles window where you will select Createto add a new role. After you give the role a new name you can begin assigning DAX filter expressions to it. Click the ellipsis next to the table you would like to apply the filter to and then select Add filter. If you select Hide all rows,then all rows for this table will be hidden (as the name implies) but if you choose a field you can apply a filter to specific values in the table. Once you are happy with your selection, hit Save. To test the security model, go back to the Modellingribbon and select View As Roles. Here you can select the role you want to test and then click OK. This will filter the result to only show your selected roles filters. To stop impersonating this role you can click Stop Viewingto return to seeing the results without this filter applied. The next step is to assign users to the roles, which must be done from the Power BI Service That means you must deploy your model to the Power BI Service first. To do that go to the Homeribbon and select Publish. Once you’ve published to the service login to Power.com and click on the ellipsis next to the dataset you just deployed.  In this menu you will select Security. Next, select the role you created and enter the email addresses of the users you would like to have the role assigned to. Click Add after you’ve entered all the users. Once you click Saveon the bottom your security is ready to go! To test it out click the ellipsis next to the role name and select Test as role. This will allow you to now view reports while impersonating this newly created role.

The September update of Power BI features an important functionality: the option to drillthough to another page in that report. For example, if a user wants to see detailed data of a product ‘Product 2’, then they can right-click on Product 2 in the main report, select ‘Drillthrough’ and the relevant sub-report to have it automatically filter the sub-report for Product 2. To do this, open your sub-report page and add any filters you require to be applied when the main report drills through to this report. For example, ‘Product’ and select ‘Used as category’. Go to the main report and select (right-click) on the Product you want to use to drillthrough, click on ‘Drillthrough’ and select the name of your sub-report. This will re-direct you to the sub-report, now filtered by the selected product. Additionally, to go back to the main report, one can simply click the back ( <- ) button on the sub-report. This feature enhances the users’ understanding of the data as well as greatly improves user experience.  

In this article, we will learn how we can leverage the work hours in Reporting. The calendar entity stores data for customer service calendars and holiday schedules in addition to business. Each calendar is set for a specific time zone. A calendar describes the availability of a service or a resource. Calendars are related to calendarrule records, which include details about the duration, start and end times, and recurring patterns of events included in the calendar. There are two types of calendar rules in Microsoft Dynamics 365: Root: A calendar rule that contains an inner calendar or that has nested (leaf) rules. You can specify an inner calendar for a root calendar rule by using the InnerCalendarId attribute. The attribute value of CalendarRule.InnerCalendarId of a root rule is the same as the attribute value of CalendarRule.CalendarId of its leaf rules. Leaf: A calendar rule that doesn’t contain an inner calendar, and therefore, is the end of the “branch.” Referred from Blog: https://msdn.microsoft.com/en-us/library/gg328538.aspx To obtain Work Hours of a resource, you can use the following fetchxml code: <fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” >   <entity name=”bookableresource”>   <!– You can use systemuser to retrieve same data –>         <link-entity name=”calendar” from=”calendarid” to=”calendarid” alias=”c” >             <link-entity name=”calendarrule” from=”calendarid” to=”calendarid” alias=”cr” >                 <attribute name=”starttime” />                 <attribute name=”effectiveintervalend” />                 <filter type=”or” > <!– These filters are applied to get calendar of this year only –>                     <condition attribute=”starttime” operator=”this-year” />                     <condition attribute=”effectiveintervalend” operator=”this-year” />                     <condition attribute=”effectiveintervalend” operator=”ge” value=”12/30/9999″ /> <!– 12/30/9999 is the max end date i.e infinite time –>                 </filter>                 <link-entity name=”calendar” from=”calendarid” to=”innercalendarid” alias=”inc” >                     <link-entity name=”calendarrule” from=”calendarid” to=”calendarid” alias=”incr” >                         <attribute name=”duration” />                         <filter>                             <condition attribute=”duration” operator=”lt” value=”1440″ /> <!– 1440 minutes equals 24 hours which is redundant. As the calendar includes Business Closures and holidays we want to avoid such calendar records  –>                         </filter>                     </link-entity>                 </link-entity>             </link-entity>         </link-entity> </fetch>

Issue: If you are trying to preview a FetchXML report in SSRS and you are a facing an issue due to a Sign-In Failure, then the reason for that most probable is due to the reason that you are trying to connect to CRM v9. When we try to connect to a v9 environment using report authoring extensions, the connection fails without any proper error and loops back to organization selection screen or login screen. If you would try to preview the same report in a v8.x environment then you would be able to preview it successfully. Reason: The main reason for this issue is that v9 only uses Transport Layer Security(TLS) 1.2 and TLS 1.0 & 1.1 connections whereas the previous CRM versions still support all TLS connections. Solution: The first solution would be to update your Business Intelligence Development Studio(BIDS) to the latest version. Please use the link below:  https://www.microsoft.com/en-us/download/details.aspx?id=56973 The second solution is to make a few changes in your regedit For systems running on .NET Framework 3.5 on x64-based systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727 Create a DWORD key Name: SchUseStrongCrypto Value: 1 For systems running on .NET Framework 4.5 or later on x64-based systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\ v4.0.30319 Create a DWORD key Name: SchUseStrongCrypto Value: 1 Restart your PC Note: Please take a backup of your regedit before editing it. Regedit used incorrectly can cause serious problems in your operating system. For x32-based systems do not add the \Wow6432Node in the HKEY paths mentioned. Your Report should preview fine now!

In the August 2018 update of Power BI, we can now apply conditional formatting based on field value. This allows us to use a measure or column that contains a color name, a hex name/code and apply that color to the background of the cells and the font in the cells of that column. For example, if I want to use color to signify the product name, we can create a calculated column to assign color names to each product as shown below: Then add that calculated column (‘Color’) to your table, and go to the Conditional Formatting dialog for ‘Color’. Select ‘Background Color’.   Select ‘Field Value’ in the ‘Format by’ drop-down menu. Since I only have one color name per row, I will select First ‘Column Name’, Summarization ‘First’  and click OK. The background color of the cells in the calculated column will now be according to the color name in the cell. If you don’t want to see the color names, repeat the steps but select ‘Font Color’ as shown below. The entire cell will now be filled. If you want to use hex names/codes instead of color names, you can create a calculated measure/column using them as shown below. Now follow the same steps as above to apply conditional formatting to the table using hex codes/names. This can help highlight sets of data easily based on their values and without the need to set rules.