Forum Discussion
Minecraft 1.21.124 Bedrock Edition Data Model Mobile Layout Refresh Error
Your report works fine in Desktop because your machine has plenty of power.
But in the Power BI Service — especially on mobile layout — the visuals are hitting capacity limits. The version filter “1.21.124” is probably returning too many rows, and your DAX + custom visual make the query even heavier.
That’s why you see timeouts, missing values, and “resource limit exceeded.”The main issues:
1. The version filter is too expensiveFiltering the fact table directly on a long text field (like 1.21.124) is slow.
Fix: Create a small DimBuildVersion table and filter through it. This reduces the load and avoids timeouts.2. Your measures are doing extra work
Distinct count of sessions duplicates → typical with wide telemetry tables.
Crash logs not aggregating → either data type or relationship issue.
Average load time missing → either blank values or the visual can’t handle the heavy query.
Fix: Use cleaner measures:
Distinct sessions
User Engagement =
COUNTROWS(SUMMARIZE(FactTelemetry, FactTelemetry[SessionId]))
CrashesCrashes = SUM(FactTelemetry[CrashCount])
Avg load timeAvg Load Time = AVERAGEX(FactTelemetry, FactTelemetry[LoadTimeMs])
3. Mobile layout is the “trigger”
Mobile renders differently and uses smaller visuals.
If your custom visual is heavy, it pushes the query over the limit.Fix:
On the mobile layout, use simple visuals only (Card, Bar chart, KPI).
Remove the custom visual from the mobile page until the model is optimized.
⚡ Quick wins you can do right now
Here’s the shortest, most practical list:
Create a DimBuildVersion and use it instead of filtering on raw text.
Remove unnecessary columns in Power Query — telemetry JSON is huge.
Fix the three KPIs using lighter DAX.
Reduce mobile visuals to 2–3 key metrics.
Test the mobile page without the custom visual.
If it works → the custom visual is the problem.
If the dataset is massive, consider incremental refresh or pre-aggregated tables.
🎯 Bottom line
Nothing is “wrong” with your report — the data size + detailed telemetry + custom visual make filtering on “1.21.124” too heavy for mobile.
Simplifying the model and visuals will stop the refresh failures.
Here is the similar issue to yours you can go through it:If this helps please ✔ Give a Kudo • Mark as Solution – help others too!
Aala Ali
Pricing & Profitability Specialist | Data Analyst at Zain Telecom
Group Leader – Microsoft Sudan Fabric User Grouplinked in profile: https://www.linkedin.com/in/aala-ali/
Most Valuable ProfessionalYour report works fine in Desktop because your machine has plenty of power.
But in the Power BI Service — especially on mobile layout — the visuals are hitting capacity limits. The version filter “1.21.124” is probably returning too many rows, and your DAX + custom visual make the query even heavier.
That’s why you see timeouts, missing values, and “resource limit exceeded.”
The main issues:
1. The version filter is too expensive
Filtering the fact table directly on a long text field (like 1.21.124) is slow.
Fix: Create a small DimBuildVersion table and filter through it. This reduces the load and avoids timeouts.
2. Your measures are doing extra work
Distinct count of sessions duplicates → typical with wide telemetry tables.
Crash logs not aggregating → either data type or relationship issue.
Average load time missing → either blank values or the visual can’t handle the heavy query.
Fix: Use cleaner measures:
Distinct sessions
User Engagement =
COUNTROWS(SUMMARIZE(FactTelemetry, FactTelemetry[SessionId]))
Crashes
Crashes = SUM(FactTelemetry[CrashCount])
Avg load time
Avg Load Time = AVERAGEX(FactTelemetry, FactTelemetry[LoadTimeMs])
3. Mobile layout is the “trigger”
Mobile renders differently and uses smaller visuals.
If your custom visual is heavy, it pushes the query over the limit.
Fix:
On the mobile layout, use simple visuals only (Card, Bar chart, KPI).
Remove the custom visual from the mobile page until the model is optimized.
⚡ Quick wins you can do right now
Here’s the shortest, most practical list:
Create a DimBuildVersion and use it instead of filtering on raw text.
Remove unnecessary columns in Power Query — telemetry JSON is huge.
Fix the three KPIs using lighter DAX.
Reduce mobile visuals to 2–3 key metrics.
Test the mobile page without the custom visual.
If it works → the custom visual is the problem.
If the dataset is massive, consider incremental refresh or pre-aggregated tables.
🎯 Bottom line
Nothing is “wrong” with your report — the data size + detailed telemetry + custom visual make filtering on “1.21.124” too heavy for mobile.
Simplifying the model and visuals will stop the refresh failures.
Here is the similar issue to yours you can go through it:
If this helps please ✔ Give a Kudo • Mark as Solution – help others too!
Aala Ali
Pricing & Profitability Specialist | Data Analyst at Zain Telecom
Group Leader – Microsoft Sudan Fabric User Group
linked in profile: https://www.linkedin.com/in/aala-ali/