This is episode 117 recorded on September 5th, 2019 where John & Jason talk to Chris Webb, Principal Program Manager at Microsoft on the Power BI CAT Team, about Power Query, data consulting, community efforts, and his new shiny new job at Microsoft.
In the current relationship view window we can delete a data table
from the model.
It would be nice to right click on the data table and click edit
query for the underlying table. This would immediately open up the query editor
for data table changes.
Today you have to switch views to the table view, and click edit table. or navigate to the edit queries button and click edit queries. Doing this opens the queries, but you still have to navigate to the table you want to change.
should be a way embedded into the Power BI Desktop or to the Power BI Service
to figure out the actual uncompressed memory footprint.
doesn’t seem to be rocket science, and would save a lot of headache. It would
allow analysts to discover how inefficient their data models are. It would
ultimately help the Power BI infrastructure as well by helping people to avoid
loading the Power BI servers with unnecessary workload.
As of now, the reports that I create on desktop utilize a lot of time intelligence functions and relative date filters. This is completely fine so long as I view the report on the desktop. Once I publish the report up to the service and then utilize those visuals in dashboards I run into this issue. All of my time intelligence functions (TODAY & NOW) and relative date filters convert to UTC.
This issue causes my data to roll over to the next day
5 hours early which affects all of my subscriptions.
It would be absolutely fantastic if Power BI service could recognize local time zone or even if we could manually set our time zone so that these measure work correctly.
I would like to have the ability to do a “compare tables” or “compare queries” option.
I understand that there are
visuals/queries I can build to compare the DATA within two separate queries but
I want to compare the two queries. I want to know how many columns are in
TableA versus how many are in TableB and which column names are different from
each other. When I have two tables with 150 columns (give or take) and they are
allegedly a copy of each other I want to be able to confirm that all 150 in
columns in TableA match all 150 columns in TableB and that I don’t have 10
unique columns in each query that just happen to come up to 150.
It would be nice to get a row count
difference at the same time, but I do know that I can do the count rows to get
that number of each.
This is episode 115 recorded on August 29th, 2019 where John & Jason talk about the latest News, Ignite update & the August Power BI Desktop news including Grouping visuals, Measure support for the Key Influencers Visual, & some new Data Connectivity.
As Microsoft increasingly supports tailored experiences, we need the ability to operate as a user with equivalent or fewer credentials, including just not being the person who added information.
For example, a site owner who made updates to a site is seeing Updated Pages (with explicit pages underneath) in the left navigation, but has no rights to remove the navigation and didn’t realize that other people weren’t seeing those pages.
Another case was where the SCA had no issue opening a document with embedded documents, but it would not open for site owners and contributors.
In our on-prem environment, I was able to use a test account and assign it with certain rights to verify that those users were going to get the experience I intended, and I was able to do that with a test account. In the SharePoint Online world, for an out-of-the-box solution I’d need a second licensed account for testing in production.
Checking permissions to a site, list, library or item helps, but just isn’t enough for testing the experience on a page in or in a solution.
A potential way to implement this would be to allow me to click on the name I’m logged in as, and in addition to About Me, Sign Out and Personalize this Page, have an option to impersonate a specific user (who has fewer or equivalent rights to me) or a certain level of rights (equivalent to or less than the rights I have).
Some developers in teams help test each other’s solutions, changing who has what rights, but for those of us who largely work independently, we don’t have that luxury.
In the query editor, queries can be grouped (and sub grouped). However, back to Power BI desktop, under the Fields pane, the queries are listed without grouping. Need to retain the same grouping. Also, when publish the dataset, need to be able to hide some query groups from the user.