Forum Discussion
Slicer visual problem
- 1 day ago
Hi John_Fjord -This looks like a potential DirectQuery-specific issue, but I wouldn't classify it as a confirmed bug yet. Since the values appear correctly in the Table visual, Filter pane, and slicer search, but not in the slicer list, I would suggest checking the following:
1. Verify that the Oracle column is defined as VARCHAR2/NVARCHAR2 and its Power BI data type is Text. 2. Check for any visual-level filters, relationships, or interactions affecting the slicer. 3. Use Performance Analyzer to compare the DAX queries generated by the slicer and Table visual. If possible, inspect the corresponding Oracle SQL for implicit conversions or differences in distinct-value retrieval. 4.Test the same column in a new slicer on a blank report page. **Using Dual storage mode is a valid workaround**, especially for dimension tables, because Power BI can retrieve slicer values from its in-memory cache instead of querying Oracle directly.
If the issue is reproducible in DirectQuery with identical filter conditions, I recommend raising a Microsoft Support ticket with a sample PBIX and query traces.
Fabric community support | Microsoft Fabric Community
Reference: Table Storage Mode in Power BI Semantic Models - Power BI | Microsoft Learn
Hope this helps!
Hi John_Fjord -This looks like a potential DirectQuery-specific issue, but I wouldn't classify it as a confirmed bug yet. Since the values appear correctly in the Table visual, Filter pane, and slicer search, but not in the slicer list, I would suggest checking the following:
1. Verify that the Oracle column is defined as VARCHAR2/NVARCHAR2 and its Power BI data type is Text. 2. Check for any visual-level filters, relationships, or interactions affecting the slicer. 3. Use Performance Analyzer to compare the DAX queries generated by the slicer and Table visual. If possible, inspect the corresponding Oracle SQL for implicit conversions or differences in distinct-value retrieval. 4.Test the same column in a new slicer on a blank report page. **Using Dual storage mode is a valid workaround**, especially for dimension tables, because Power BI can retrieve slicer values from its in-memory cache instead of querying Oracle directly.
If the issue is reproducible in DirectQuery with identical filter conditions, I recommend raising a Microsoft Support ticket with a sample PBIX and query traces.
Fabric community support | Microsoft Fabric Community
Reference: Table Storage Mode in Power BI Semantic Models - Power BI | Microsoft Learn
Hope this helps!