Forum Discussion
Post ProdigyHow to display zero using Measure or column value (when there is no value)?
I would prefer you don't do that. Instead, enable "Show items with no data".
Post ProdigyThank you so much for your help again! 🙂
I uploaded my concised and data-safe version into my Google drive here .
There are three tabs/parts ( Actual, Variance and Budget) on this PBI file.
What you would see here is that because "Kyle" does not have "Census Data" for Actual, it would not reflect on the other visuals in both Actual and Variance tabs.
Is it possible to show 0s (on the missing lines)?
Thanks.
Super UserYou need to do a lot of work on your data model before you can think of that
You need to create a Facilities dimension table and then merge it with the trend and occupancy tables. Then you need another PayerType dimension , and then youcan connect your dimensions to your fact without the need for a joinkey table.
- JustinDoh1
I was working pretty much all day with relationships.
I thought that "joinkey" table would work, but I will definitely restructure my relationship tomorrow based on your suggestions and let you know where I am at. Thank you so much!!
BTW, what do you mean by "merge"?
Do I have to combine two tables (like "trend" and "occupancy" tables) or you meant connect with Facility dim table with "trend" and "occupancy" tables?
- JustinDoh1
Can you please take a look at my updated PBI file here that has two additional dim tables (tblFacility & tblPayerType)? I deleted all relationships from my previous "JoinKey" table.
I am not sure how to connect tblFacility with 3 fact tables.
Actually, I am lost in many ways 🙂
Also, I am not sure why on the "Actual" tab, it shows fewer columns (4 instead of 6) than others.
Appreciated.
- lbendlin
Merge these tables
Bidirectional 1:1 between two tables usually indicates that this should be a single table.
This is not yet a dimension table. It is missing a primary key. Figure out what the primary key is and kick out/downstream anything that prevents it from working.
Avoid bidirectional *:* relationships wherever possible. They are expensive and can lead to wrong results.
- JustinDoh1
Ok. Thank you so much for your feedback.
I will work on it again tomorrow and let you know 🙂