Hi @smithjoe ,
If you would like to suggest feature improvements, you may vote the idea and comment here to improve this feature. It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
Best Regards,
Community Support Team _ Caitlyn
Hi @smithjoe ,
If you would like to suggest feature improvements, you may vote the idea and comment here to improve this feature. It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
Best Regards,
Community Support Team _ Caitlyn
Hi @stugardner1037 ,
From the post you shared, the issue appears to be a known issue and is being fixed. You can be patient and wait for the issue to be fixed.
Best regards,
Community Support Team Selina zhu
429 error indicates that too many requests have been sent in a certain period of time. When many refresh plans are refreshed at the same time, the model used for refresh will be loaded. Once there are too many models in the memory, the memory will become full. The model generated by the subsequent refresh operation cannot be loaded and enters a queued state, so that the report will be loaded slowly or fail.
You can try to refresh this data source in some other time ranges to check this issue again.
Best Regards,
Community Support Team _ Yingjie Li
Hi @Barry_Smart ,
We have submitted to internal ICM 304873937 , the status of this thread will be changed to Accepted to prove that this is a bug confirmed by Microsoft.
We have gotten some feedback from the PG team:
“The cyclic reference is because the record field name is Schema, and the customer is trying to assign the value of Schema to be Schema. This means that in order to evaluate the "Schema" field, the engine first has to evaluate the "schema" field, producing infinite recursion. This is not a problem with the connector, but with the customer's mashup query. Query editor uses different queries to produce (and refresh) the preview data, so the cyclic reference does not become immediately problematic until refresh when the customer's query is ran.
There is a simple mitigation for this: clients may avoid using schemas that have a name called schema, or referencing them from a different schema name.”
The bug has been submitted but there is no clear time frame for fixing it yet. Engineers are trying their best to solve this issue, please be patient and I will give you feedback here once there is any progress.
Best Regards,
Community Support Team _ Caitlyn
Hi @Amicci ,
There are indeed users who also have this problem, which has been reported to ICM , the id is 348173711.
I'll be back with an update if there's any progress .
Best regards,
Community Support Team Selina zhu
After testing, the issue has now been fixed.
Hi @CRIS_9
I can export the decomposition tree visual to PDF in 30sec . Did you export the visual with Export PDF ? If yes , you can check the Considerations and limitations in the following URL to see if these limitations are causing the problem .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @DouweAtAlfa ,
I investigated your error through this doc:
Troubleshoot XMLA endpoint connectivity in Power BI - Power BI | Microsoft Docs
it says some situation may cause the error as yours, eg:
Through these options maybe can avoid error:
Best regards,
Community Support Team Selina zhu
Hi @lale24
This is happening because PG gradually upgrading UI as part of Trident effort so this is a new component intended to replace old functionality.
PG gives a workaround : to apply `?tridentStageTwo=0` flag to url .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @mookje77
Can you access your reports on Service normally now ? I have not seen a similar known issue so far . If you have been able to access it normally, please reply to me. If not, please provide more detailed information for reference.
Best Regards,
Community Support Team _ Ailsa Tao
PG team is still working on this issue.
Could not reproduce it in my side as far as my test. The paginated report works fine in Power BI Service.
Thanks for @MikeWall provided information that it has been acknowledged as a bug by MS, and we will still continue to investigate this issue, if there is any progress, would update here.
Best Regards,
Community Support Team _ Yingjie Li