Let's Get Organized With Power BI

Organization for me is always a priority. When things are not in the right place and I can’t find something quickly I get frustrated. This is not only in my daily home life when trying to find a tiny car that my son remembers from 2 weeks ago and he now has to have to continue playing, but also in my Power BI report building.

When building DAX measures on a report, some users think the measure has to be on the table they are referencing. The fact of the matter is a DAX measure can be on any table no matter the reference and it will still run properly. Due to this, I like to put all of my measures on a dedicated table so they are easy to find for me and my end users. This table is not a data source table, but one I create within the report itself. You might be asking will this extra table affect the performance of my report or the data refresh. It will not! Let me walk you through the process of how easy it easy to make your measures table and organize it in your field’s pane.

Step 1: From the Home ribbon of the Power BI Desktop, select the Enter Data icon.

Step 2: Give your table a name and select Load. If you haven’t noticed yet, the Fields pane has all the tables listed alphabetically. I used this to my advantage and I give my table the name “/Measures”. The “/” in the front of the name will promote my table to the top of the field’s pane.

Step 3:

Start making your measures within the table. After you make your first measure, you can delete the column that was auto-created in the table if you wish.

Step 4:

There are other ways to organize measures within a report. Some like to create a folder in the Model view and place all columns of each in a folder and all measures outside of the folder. You just need to find what organization system works best for you.

If you enjoy this blog and are interested in formal training on Power BI, Power Apps, Azure, or other Microsoft products you can use my code "Matt20" at check out when purchasing any private training or On-Demand Learning classes from https://pragmaticworks.com/pricing/

Comments

Best Practice To Trim Before Removing Duplicates or Merging In Power Query Editor

In last week’s blog, I wrote and did a video about how to remove duplicate records and keep the most recent entry as long as a date column was part of the data source. I came across the scenario while giving training on Power BI with my company Pragmatic Works. See the video below: This week, while doing another two-day training I came across a different scenario from a follow-up conversation from day 1. I had explained how to remove duplicate records and one of the students started working on a Power BI project she has for her company. On day 2 the student informed me that her remove duplicates step was not working. I said that is odd and I asked to see the data. In one of her table visuals, I could see that it appeared that a few of the records had duplicates based on the name column. After further investigation though, we figured out the culprit. She had done all the steps correctly, but it was a data integrity issue. In her data source, the perso

Relating "Related Tables" to Baseball because I Miss Sports

I miss sports. In particular, I miss baseball. Between learning more Power BI functions and the ins-and-outs of DAX, I've turned to Netflix to fill the deep caverns left in my soul since baseball season has been postponed. And as a result, I've thought more about tigers and big cats more than I ever have in my life. I know ALL about Carol Baskins and am fully on board for a spin-off centering on locating her lost husband. I've googled "is it really legal to own a tiger in a residential area?" Without baseball in April, I am barely hanging in there (kinda like Joe Exotic's eyebrow ring). So, I am filling the sports-sized hole by using baseball stats in Power BI to demonstrate pulling data from multiple tables and consolidating it into one table. Some of the data we want to consolidate also has to have some aggregations (which is fancy for "calculations") performed on it. In this demo I will attempt to break down what is really going on

Create A Record Without A Form In Power Apps Using PATCH

In Power Apps, forms are great to use to submit data to be recorded in your data source. They do not take long to set up and the functions used to submit the data are fairly simple. This simplicity, however, can come at a cost. The cost of using a form is you don’t have a lot of design control in terms of layout and design. If you don’t like the rigid structure of forms and want more freedom, then I’ve got the fix for you. You need to become acquainted with the Patch function. The Patch function allows you to update or create a new record in your data source. The Patch function requires you to identify your data source, decide if you want to update or create a record, and then point to your controls on the app that contains the data you are submitting. The coding is a little more involved compared to SubmitForm(FormName) that you use on forms. The payoff, though, for learning a little more advanced code is you get complete design freedom for your data input controls.

The Algebra Teacher Powers to B.I.

Search This Blog