Visual Not Loading When Using Hybrid Tables

[harsha_nalwad]

I have two tables, A and B, connected with a one-to-one relationship. I’m trying to create a visual using fields from both tables: A[col1] and B[col2].

Here are the scenarios I tested:

1. Scenario 1:
   Both tables A and B are in DirectQuery mode → The visual loads without any issues.

2. Scenario 2:
   Both tables A and B are in Hybrid mode → The visual does not load; it keeps refreshing indefinitely.

3. Scenario 3:
   Table A is Hybrid, and table B is DirectQuery → The visual does not load; it keeps refreshing indefinitely.

What is causing this problem and how do I resolve this ?
Note: Both of the tables are having 6000 records each and both of the tables are refreshed, table A has got the partitions after the refresh and table B has a direct query partition.

[v-kpoloju-msft · Accepted solution]

Hi @harsha_nalwad,

Thanks for explaining the scenarios clearly. In addition to the solution shared by the community member @MasonMA, below, here’s an alternative approach you can consider.

Since the visual works when both tables are Direct Query, the issue isn’t data size or the 1:1 relationship itself. The problem occurs when Hybrid tables are involved. In a Hybrid + Direct Query setup, Power BI decides at query time whether to use Import mode or Direct Query mode. When one table contains imported partitions and the related table is Direct Query-only, Power BI can repeatedly switch execution paths, causing a query planning loop which is why the visual keeps refreshing indefinitely.

To resolve this, align storage modes across the related tables (both Direct Query, or both Hybrid with consistent partitioning). If possible, avoid 1:1 relationship with Hybrid tables and prefer a star-schema (1:*), or merge the tables upstream. For small lookup tables, setting them to Dual can also help Power BI resolve joins in memory. These approaches follow Microsoft’s composite model best practices and should prevent the infinite refresh behaviour.

Refer this link:
1. https://learn.microsoft.com/en-gb/power-bi/transform-model/desktop-storage-mode 
2. https://learn.microsoft.com/en-gb/power-bi/guidance/composite-model-guidance 
3. https://learn.microsoft.com/en-gb/power-bi/transform-model/desktop-composite-models 

Hope that clarifies. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @harsha_nalwad,

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

[v-kpoloju-msft]

Hi @harsha_nalwad,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[MasonMA]

Hi;

I tested tables with 30,000 rows (one to one, Storage mode changed from DirectQuery to Dual) and the visuals load correctly. It looks the issue you experienced is not a simple deterministic storage-mode limitation. There’s likely something specific to your model, partitions, or environment that triggered it.

I'd suggest sharing more details about the setups, like partitioning details or visual configurations.. 

[v-kpoloju-msft]

Hi @harsha_nalwad,

Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to @MasonMA,  for those inputs on this thread.

Has your issue been resolved? If the response provided by the community member @MasonMA,  addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

Thank you for using the Microsoft Community Forum

[v-kpoloju-msft]

Hi @harsha_nalwad,

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.