Forum Discussion
Table Relationship Excluding Values
Read about AutoExist AutoExist and Normalization - SQLBI
Please provide sample data that covers your issue or question completely.
https://community.powerbi.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-Forum/ba-p/963216
Please show the expected outcome based on the sample data you provided.
https://community.powerbi.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447523
I appreciate your response. I don't think it is an issue of auto exist.
If you look at the datatable on it's own, I get 318 rows that have that specific value.
If I join that first datatable with a second datatable, and create a table visual, I only get 250 values. BUt I do get the row based on the member ID as a key.
For security reasons, I am unable to provide my PBIX file.
Please provide sanitized sample data that fully covers your issue. This does not have to be your actual data.
Please show the expected outcome based on the sample data you provided.OK, here's a very simple version. The Master table has an ID for all MBR. The Conditions table has a Many-1 relation with the Master. A member can have 0, 1, or more Conditions.
The Export Summary should have a row for each row in the Master and any matching data in the Conditions.The desired result would look something like this:
OK, I think I have solved the issue in my real (much more complex) example. Turning on Show Items with No Data fixed the sample setup shown above.
But, what I think has fixed the original issue is the ordering of the columns. I had some columns from table 1, then some from table 2, more from table 1 and finally some from table 2. If the columns are ALL set to Don't Summarize, BI is essentially performing a "group by" on each column, and by having them in the "wrong" order, I was getting unintended consequences.