The Algebra Teacher Powers to B.I.

    Have you used the personalize visuals feature yet in Power BI?   If not, then you could be missing out.   The Personalize Visuals feature allows anyone you are sharing your with after published to the Power BI service to make changes to your visuals.   Have no fear though!   When they change the visuals it will not override your original report.   This feature is great if you have ever had to respond to a request from your shared users that they would like the report to be modified to their liking.   With this simple feature, the end-user can change the visualization type, change what measures or fields that are brought into the visual, and then simply make a personal bookmark after they make the changes.   Again, this will not change the initial report you published and that others have access to.   This will only make a new view of the report for the user who personalized the visual.   If you decide to use this feature...

  Power BI came out with a new preview feature in the February 2021 version of the Power BI Desktop known as small multiples.   To use this feature as of the May 2021 release, you need to turn on this feature in your preview features.   The small multiples feature allows you to take a bar/column, line, area, or combo chart visual and essentially duplicate the visuals on the page with each one being uniquely filtered down by a specific dimension.   For example, you could split a column chart that displays your sales by country into unique duplicates that report for each year.   To create the small multiples you will drag the field that you want to dissect your original visual by into the Small Multiples field in your visualization pane.   After seeing the new result, if you want to have even more control of how the visual is display check out the Small Multiple Title section and Grid Layout section in the formatting area of the visualizations pane. ...

In the Power BI Desktop, you are allowed only 1 active relationship between tables in your data model.  Many times this is all that is needed.   There are, however, scenarios where this becomes a huge reporting issue.   For example, what if you have a table of sales where one column contains the date a sale occurs and another column that records the date the money from the sale is collected.   Well, depending upon which relationship is active with your Date table in your model the sum of your sales will either be based on the sale date or the money collected date.   If you need to see both values though this is where you need to make a separate measure using the function USERELATIONSHIP paired with the function CALCULATE.   The USERELATIONSHIP function will allow you to access inactive relationships in your data model.     Another scenario, where I have seen this be an issue, is when users need to see their sales based on the city where t...