Matrix does not slice and dice other visual in Hybrid mode

[PowerBIExpert]

We have a report based on a shared dataset containing just two visuals: a matrix and a table and data model consists of two tables.

The matrix visual contains only 2 fields - e.g., Table1.Column1 and Table2.Column1 while the table visual contains the same Table1.Column1 and Table2.Column1 fields plus other fields from tables 1 and 2.

Table1 was converted into hybrid table using the option in Incremental Policy "Get the latest data in real time with DirectQuery (Premium Only)" and Table2 is in dual mode.

On Power BI Desktop the report works fine and selecting a value in the matrix, filters the table visual accordingly.

However, once the report was published to Power BI service, noticed that Table1.Column1 values are filtered ok in the table visual but whenever selecting a Table2.Column1 value in the matrix, the table visual will go instantly blank (because of direct query, filters take a few to seconds to apply, but behavior with Table2.Column1 happens instantly in the table visual, so it doesn't even seem to try to run a query).

Also, both the matrix and table visuals are filtered ok if we use a filter or slicer.

This issue does not occur if the Table2 is either Direct Query or Import or both tables are either Direct Query or Import, it happens only if Table1 is hybrid and Table2 is Dual.

Due to huge data and slow performance and business requirements, Table2 has been made as Dual.
P.S.  the issue started happening recently, June and July releases.

Any idea how to fix report behavior in Power BI service?

[hackcrr · Accepted solution]

Hi, @PowerBIExpert 

Make sure that the incremental refresh policy for Table1 is set correctly and does not interfere with the DirectQuery functionality. You may want to check to see if any recent changes have been made to the refresh policy.
Assuming Table2 is in Dual mode and Table1 is in Hybrid mode, make sure your model is optimized for performance. Check to see if there have been any recent performance tuning or optimizations that might affect behavior.
Try using different visuals (e.g., cards, charts) rather than a matrix to see if the behavior persists. This can help determine if the problem is with the matrix visuals or with the data model/filtering.
Possible solution.
1. Temporarily convert Table2 from Dual to Direct Query and see if that resolves the issue. If it does, confirm that the problem is in the processing of the Dual schema.
2. As a temporary measure, filter the table visually using a slicer or filter rather than selecting values directly in the matrix.
3. If possible, reduce the amount of live data being extracted using DirectQuery. This will help determine if the problem is due to the amount of data being queried.

hackcrr

If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly