Forum Discussion
Helper IShared Dataset visuals failing - original dataset functions correctly (BigQuery Datasource)
Hello,
I am leveraging Power BI shared datasets to power several reports that all share the same data model. For some reason the report "front end" that leverages the Power BI dataset, performs worse and some visuals won't load (resources maxed), but the original dataset (import connection to big query) works just fine.
"Original Dataset":
- Import connection to bigquery
- Pulls in a dozen or so tables (max rows ~1MM)
- Published to workspace for others to consume
- All visuals render (some fairly slowly)
"Shared Dataset":
- 14 Reports all leveraging the same data model + calculations as the orginal
- Difference between reports is that each report is filtered to a specific functional area / location and shared with those users.
- Each report sits in a different workspace and is distrubited as an app.
- Most visuals (weekly & daily rollups) run slow, but do render
- One visual consistently fails across all reports using the shared dataset (table visual)
Questions:
- Why would the report work in using the original dataset (report + dataset published to a workspace)?
- The only way I've been able to detect poor measure performance is to create variants of the visual in question and remove one measure from each varient and run the performance analyzer on it. Is there a better way to do this?
4 Replies
Hi accortdr ,
Could you please explain the first question with more details? Sorry I cannot understand it correctly.
The performance analyzer is a tool, built in to Power BI, that can help you to find different aspects that make your report to run slowly.A great video of the Performance Analyzer by SQL BI can also be foundhere.
For each visual, we can see three headers as well as a number besides them:
- DAX query
- Visual display
- Other
More details: Tips to increase the performance of your Power BI Reports
Optimization guide for Power BI
Boost the performance of Power BI with these analyzer tools
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
accortdrThanks Anonymous ,
Performance Analyzer:
I've used the performance analyzer, but the "Dax Query" is the full query made back to the query engine, which is kind of useful, but I have 15 measures or so which I am not able to differentiate between in the PA output. This makes it difficult to debug / optimzie my individual measures.
Could you please explain the first question with more details? Sorry I cannot understand it correctly. :
- When I publish the original report (import connection to BigQuery), the report renders correctly in the Power BI service. Lets call it Report A + Dataset A
- I developed a second report (live connnection to Dataset A) that has all the same visuals as Report A. This live connection report exceeds the visual's resources (see below for error message).
- This is confusing because the original report works fine, but when I create live connected reports off of that original dataset, it breaks down.
- Please let me know if that still needs further clarification.
Hi accortdr ,
the issue occurs when a visual has attempted to query too much data for the server to complete the result with the available resources.
As suggested in the error, you may need to try filtering the visual to reduce the amount of data in the result currently.
More details: Troubleshooting tile errors
Here is a blog, please refer to it to see if it helps you.
The “Visual Has Exceeded The Available Resources” Error In Power BI
- Tune the DAX calculations used in this visual
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
