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

Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more

Share your ideas and vote for future features

Status: Investigating
Status: New
Status: Needs Info
Status: New
  • Report Server
Status: New
Status: Investigating

Still could not reproduce it in my side as far as my test, after I have deleted the scorecard from Metrics, have not received refresh failed e-mail during these days.

 

If this issue is urgent for you, suggest that you can create a support ticket and the end of the support page for further fast help, see:

Support | Microsoft Power BI

vyingjl_0-1660721742601.png

 

Best Regards,
Community Support Team _ Yingjie Li

 

  • Report Server
Status: Accepted

There is the same issue here and you can find the expected fix date about it and potential workaround:

https://community.powerbi.com/t5/Issues/Issue-Can-not-publish-power-bi-app/idc-p/2668626

 

Best Regards,
Community Support Team _ Yingjie Li

Status: Investigating

Hi @sobhark,

 

May I know what’s your data source and what’s the connection mode? What kind of capacity is your report workspace in? Is this issue happening on the reports in a specific workspace or randomly happening on all your reports?

Is your report data large? Is your report page containing too many visuals?

 

Best Regards,

Community Support Team _ Caiyun

Status: Accepted
Status: New
Status: Investigating
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: Investigating

Hi @HSpeelman ,

 

It seems like you’re doing everything correctly according to the documentation. The property should indeed provide a hint regarding the data that is covered by the partitionDataCoverageDefinition. This property is supported when the compatibility level of the database is at 1603 or above, which is the case in your situation (1604).

However, if the property is not found when re-opening the script of the data model, it might be due to some issues with the deployment process. You could try using the Deployment Wizard for deploying model solutions. It uses JSON output files generated from an SQL Server Analysis Services project as input files, which are easily modifiable to customize the deployment.

 

You may refer to Deploy model solutions by using the Deployment Wizard | Microsoft Learn

 

Best regards.
Community Support Team_Caitlyn

Status: Delivered

After testing, the issue has now been fixed.

  • Report Server
Status: Needs Info
Status: Accepted
  • Report Server
Status: Delivered
Status: New
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

Idea Statuses