I have a report like this:
It's got three tabs, based on three separate SQL queries (and Power bi queries) of our database.
One tab is based on all the subjects we have in our program
One tab is a query of a database with all the staff associated with all the
subjects in our database
The third tab (that I am working on now) is from a query of all the subjects in our database that need reconsent. The way I envision all three tabs working is that you start in the first tab, filter to the subjects you care about, and then those slicers/filters affect the next two tabs.
My problem is:
I dont know how to get the slicers/filters in the first tab to affect the others. I was able to get the second tab linked by just merging those two queries (there's pretty much 100% overlap) and just using "one" dataset for both.
I've tried "manage relationships" and created a relationship between the first query subject mrn and the third query subject mrn... but even though there's a 'relationship' between the two... thats not enough for slicers on the first tab to affect anything on the third tab. How do I do that?
I asked this on the power bi forum as well and was given some followup questions that I'll add info from here:
The sync slicers setting is on:
And if I go look at the table on the third tab, it says a bunch of slicers are currently affecting it:
(I changed the slicer values between taking these screenshots, dates look different in each)
Also here is a photo of the relationship between queries in the model:
So to repeat/rephrase:
Let's say I use slicers on the first tab to filter to 10 people coming in the next week (which are in one query). Lets say 1 of those people exists in the third query as someone who needs reconsent. How do I get only that one guy to show up on the third tab with his info from that query?
Related
I have a Power Bi dashboard that looks like this:
But I dont want all the rows of everyone's data to show up. Ideally its single select only, these results look great when only Elizabeth is selected (not sure why screenshot looks like two people):
Because I want to stack quite a few other tables in the dashboard that are one row only, like so:
So my question is: how can I force the name slicer on the left to ONLY allow one person to be selected, and never be 'not' selected where lots of people are involved? Does that make sense?
That is a table and not a slicer. Tables will display everything you ask them to. If you switch it to a slicer, you can make it single select.
Tableau automatically groups measures together but Power BI Desktop doesn't natively support this. I find it annoying to have to place measures under imported tables as the measures don't really belong to those "parent tables" (and quite often take input from multiple tables — which one would you consider the "parent"?)
So I experimented with some workarounds and I'm sharing the successful (as of the date of this post) ones here:
Method 1 (recommended): "Model" view > "Enter data" to enter a manual data table. Give a name like "_Measures_" so it appears on top of tables, and keep only the default dummy column "Column". Create/move measures under it, then right click to delete that "Column". Now you're left with a blank table that groups those measures under it.
Method 2: "Data" view > "New table" to create a DAX calculated table. Rest the same as above, except that for a DAX calculated table you can't delete the dummy column but instead you can hide it.
You can also "Enter data" using Power Query Editor but I don't recommend going with that extra step -- workarounds are supposed to be quick (and dirty) anyways!
Final results look like this (note the difference of the icons):
Hello I am trying to raise awareness about his subject I am facing this issue, I've posted on microsoft PBI community as wel, Did you even know about this, if so, how did you do to workaround this?
https://community.powerbi.com/t5/Desktop/Beware-Misleading-behaviour-using-Select-all-or-none-selected/m-p/1982650#M749494
As stated in the post, I have just found half a paragraph hinting about this behaviour and all the people that I've talked to did not even know it behaved this way.
TL:DR. If you use the filter panel to filer a slicer (filter on this visual) in order to restrict the selection of a slicer (so your end user does not get lost in too many options or you want a dynamic slicer showing last x months, TOP N , basically any other advanced filtering optins given using this feature).
It only visually filters the slicer so if the user ends up using "select all" or even clearing the selection, all the data would be selected even the data you (as designer) wanted to filter out. Which is misleading since the end user would see the tag "all" over the slicer selection but when clicking on it it would only show the filtered out values, so they would naturally assume that "all" means just those values and not allvalues (hidden values included).
Example
there are only two values to be selected in the slicer but the select all option actally seelcts all values including hidden ones
One thing to check first, I bet you did not apply the filtered values in the filter pane on the whole page, rather you applied it only on the visual. Try to apply that on the whole page and it seems to work for me.
I currently have two tables: A "Send ID" table and an "Affiliation Table" each based on a column of customer IDs.
No columns have purely distinct values so I cannot create a many to one relationship.
I would like to visualize the Send IDs based on the Affiliations as shown here:
Desired Output
I can work with either having the Send IDs repeat per affiliation in the new desired table or have them unique per affiliation - either way works with me.
Any help would be appreciated.
Thank you
noyraz's solution in establishing a many to many relationship based on the customerID should suit your needs.
If you are required to find out where a customer appears in the affiliation table or sendID table, I highly recommend performing a full outer join in the query editor.
Using the picture below, right click on any of the tables, and select reference.
Reference Screenshot
Then rename the table if you like
Click on Merge Queries
In the drop down, select the other table you didnt reference, then click on both customerIDs
select full other join.
Full Outer Join labled screenshot
Expand the new table column
deselect the ID if you like.
Expanding Column Screenshot
If there are occurrences where they don't appear (useful for sending and delivered tables), you can do visual level filters to see where either the Affiliation or SendID is null/blank.
when you create Many To Many relationships like Here
all you have to do next it's just visual this like you desire
hope I understand your question right
I'm new to Power BI but am not seeing something that I feel should be pretty common report functionality. I have a cognos report that has a list grouped by specific fields, each item in the list has fields, etc. Each "item" is repeated in the list.
Can Power BI do something similar to this functionality? I have been looking at multi-row cards, tables, etc. but I'm not seeing a repeater control or something that would allow to mimic this functionality? The multi-row cards would work but I can't style them how the customer wants or needs b/c they are printed and need to match a certain format.
Even the single cards, if I could drop all the fields I need as single cards, format them how I want. Is there a way to have all rows repeated in a "list/set" of those single cards? Right now when I drop a bunch of single cards and a splicer it displays the first record and that is it? Surely there is a way to get all the records.
Here is an example (I need the formatting to remain basically the same, each row from data source represents one page that looks like this)
Thanks,
Tim
I don't think this is possible in Power BI yet. A muti-row card has similar functionality, but is not customizable enough to match what you are trying to do. Custom formatting is one of the drawbacks of Power BI at this time.
You can vote for this idea on the Power BI Ideas site, but I'm guessing it's not a high priority for Microsoft for now.