Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Share your ideas and vote for future features

Status: Delivered

Hi @hugo-gomes 

Issue is mitigated in all regions except CANADA central. ETA for Canada is 19th .

 

Best Regards,
Community Support Team _ Ailsa Tao

Status: Delivered

Hi @sgrewal @ricardcom ,

Glad the problem was disappear, then I will close the thread.

 

Best regards,

Community Support Team_yanjiang

Status: New
  • Report Server
Status: New
  • Report Server
Status: Accepted

Hi @karma123 ,

 

We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

 

Best regards.
Community Support Team_Scott Chang

  • Report Server
Status: New
  • Report Server
Status: Accepted

Hi all,

 

The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

 

Best regards.
Community Support Team_Caitlyn

  • Report Server
Status: Accepted
Status: New
Status: Accepted

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

Status: New
  • Report Server
Status: Delivered

Update:

Engineers have identified the root cause and a fix is expected to be deployed by end-of-day 08/20/2022

 

Best Regards,
Community Support Team _ Yingjie Li

Status: Delivered

After testing, the issue has now been fixed.

  • Report Server
Status: Investigating

Hi @kiaklee 

You can try to go to Power BI service, Get Data-> Files to get pbix files, this has the same effect as publish from desktop. If you can get file successfully , there may be a problem with your Desktop, you can uninstall and reinstall the Desktop to see if it works .

 

Best Regards,
Community Support Team _ Ailsa Tao

  • Report Server
Status: New
  • Report Server
Status: Investigating

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

Status: New
Status: New
Status: New
Status: Delivered
Idea Statuses