Forum Discussion
Direct Query Filtering Values in Visual based on another Columns Values
Hello,
Using PBI Direct Query data, I have a table where I need to show specific (or group of specifc values) based on another columns values. Using a table visual, I want to only show the data that shares values in the "VIS" column. Due to work confidentiality I cannot share the pbix file, but example data and desired output below.
The key here, is I only want to show data that has more "Lots" associated to it than just the original. As an example A123 with v111 will show because it is associated to more lots, v122, v33 would not show.
For a little more context, this page utilizes a drillthrough so a customer can drill on the Lot and understand all the variants of the VIS and which other Lots are associated to the VIS. I have another data table that uses a connection to "normalize" the Lot values whether it ends in "r" or "rv".
Example Data
| Lot | VIS |
| A123 | v111 |
| A123r | v111 |
| A123rv | v111 |
| A123 | v122 |
| A123 | v133 |
| B124 | v144 |
| B124r | v144 |
| B124rv | v144 |
| B125 | v155 |
Desired Output
| Lot | VIS |
| A123 | v111 |
| A123r | v111 |
| A123rv | v111 |
| B124 | v144 |
| B124r | v144 |
| B124rv | v144 |
Hi ChazTime,
Thank you for your detailed follow-up and your efforts in debugging the scenario.
While the ShowVIS logic functions correctly in a straightforward setup, the inclusion of additional filters such as Loc ID in a DirectQuery model may cause the measure to malfunction. This is due to the manner in which DAX is evaluated and translated into SQL. When complex filters are applied or measures rely on CALCULATE logic involving related tables, Power BI’s query folding can behave unpredictably in DirectQuery mode. This may result in incorrect or uniform outputs, for example, all values being 1.
Kindly consider the following workaround options which might assist in resolving the issue:
- Use a SQL view to pre-aggregate or filter the data at the source.
- Employ a composite model (Import + DirectQuery) for enhanced flexibility in DAX.
If you find our response helpful, please mark it as the accepted solution and provide kudos. This will help other community members encountering similar queries.
Should you have any further questions, please feel free to reach out to the Microsoft Fabric community.
Thank you.
9 Replies
- lbendlin
Super User
Change your point of view. Group by VIS, and only show VIS that have a Lot count greater than 1.
Hi lbendlin ,
I have tried that as well but most counts are showing as only a one, even if using distinct, even though it has multiple records. It might be do to the other columns I am adding to the table. For example expanding a bit, I could have VIS Results where its only showing 1x in the Lot but will also have a record with an R or RV Lot too. See below.
Also, the ending result isn't always a "Pass" could all fail too.
ExampleLot VIS Result A617 002 Fail A617R 002 Fail A617RV 002 Fail A617RV 002 Pass A617 001 Fail A617 001 Pass A618 003 Pass Desired Output
Lot VIS Result A617 002 Fail A617R 002 Fail A617RV 002 Fail A617RV 002 Pass 
v-pnaroju-msftCommunity Support
Thankyou, lbendlin, for your response.
Hi ChazTime,We sincerely appreciate your inquiry on the Microsoft Fabric Community Forum.
Kindly find attached the screenshot and PBIX file, which may assist in resolving the issue:
If you find our response satisfactory, we would be grateful if you could mark it as the accepted solution and kindly provide kudos. This will help other community members who may have similar queries.
Thank you
Hi v-pnaroju-msft ,
Thank you for the response and pbix file. Unfortunelty your solution cannot work because I am using a Direct Query. The 'CALCULATE' function is not allowed. I changed from a calculated column to a measure but it still did not work. See error below.
- v-pnaroju-msft
Hi ChazTime,
Thank you for your response.
Since you have mentioned that switching from a calculated column to a measure did not resolve the issue, please consider the following points that may affect the behavior of the measure:
-
Visual-Level Filter Application.After creating the measure (for example, ShowVIS = IF([DistinctNormalizedLots] > 1, 1, 0)), kindly ensure that it is added to the visual-level filters pane and set to display only when ShowVIS = 1.
-
Normalized Lot Column.If you are working with Lot variations such as A617, A617R, and A617RV, it is necessary to create a normalized version of the Lot (for instance, by using Text.Start([Lot], 4) in Power Query) to ensure consistent grouping by VIS across these variations.
-
Model Structure.If a related table is being used to map or normalize the Lots, please verify that the relationship is active and that the measure references the correct column from the appropriate table.
Please find the revised PBIX file attached, which may help to resolve the issue.
If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members who may be facing similar queries.Should you have any further questions, please feel free to contact the Microsoft Fabric community.
Thank you.
-
- v-pnaroju-msft
Hi ChazTime,
We have not received a response from you regarding the query and were following up to check if you have found a resolution. If you have identified a solution, we kindly request you to share it with the community, as it may be helpful to others facing a similar issue.
If you find the response helpful, please mark it as the accepted solution and provide kudos, as this will help other members with similar queries.
Thank you.Hello v-pnaroju-msft ,
Sorry for the late response. I have been debugging for a few days. Initially your resolution worked but putting any additional filter completely breaks the table. The data set is very dynamic, there is an additional column used as a "Location" code, and adding that filter is what breaks the table. Additionally, when drilling through on different Lots, the table still is showing all data as the "ShowVis =1" filter is showing all values as a 1. I am not 100% sure why it is doing that but still debugging the issue. As an updated table this is the additional column.Lot VIS Result Loc Loc ID A617 0001 Pass 6000 X2 A618 0002 Fail 6001 X1 A618R 0002 Fail 5001 X1 A618 0002 Pass 6002 X3
Desired Output: (Added additional filter for Loc ID = X1 onlyLot VIS Result Loc Loc ID A618 0002 Fail 6001 X1 A618R 0002 Fail 5001 X1 I am tempted to close this and accept as a solution because I think in a more straight forward dataset this solution works, but with the direct query it does not.
- v-pnaroju-msft
Hi ChazTime,
Thank you for your detailed follow-up and your efforts in debugging the scenario.
While the ShowVIS logic functions correctly in a straightforward setup, the inclusion of additional filters such as Loc ID in a DirectQuery model may cause the measure to malfunction. This is due to the manner in which DAX is evaluated and translated into SQL. When complex filters are applied or measures rely on CALCULATE logic involving related tables, Power BI’s query folding can behave unpredictably in DirectQuery mode. This may result in incorrect or uniform outputs, for example, all values being 1.
Kindly consider the following workaround options which might assist in resolving the issue:
- Use a SQL view to pre-aggregate or filter the data at the source.
- Employ a composite model (Import + DirectQuery) for enhanced flexibility in DAX.
If you find our response helpful, please mark it as the accepted solution and provide kudos. This will help other community members encountering similar queries.
Should you have any further questions, please feel free to reach out to the Microsoft Fabric community.
Thank you.
Thank you for the solution and time v-pnaroju-msft . I am looking at option 1 and if I have too, will change to import mode. Accepting solution.
