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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Share your ideas and vote for future features

Status: Accepted

Hi @Omar_Osman ,

 

Power BI now has a problem connecting to SQL endpoint.

We have reported this issue and submitted it to the product team.
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient. 

 

Best regards.
Community Support Team_ Caitlyn

 

  • Report Server
Status: Accepted

Hi all ,

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 ! Thank you for your cooperation !

 

Best Regards,
Community Support Team _ Ailsa Tao

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

HI all,

This issue has been fixed , please check it in your Service .

 

Best Regards,
Community Support Team _ Ailsa Tao

  • Report Server
Status: Delivered

Hi @AHeyman_ 

This issue has been fixed , Please check it in your broswer .

 

Best Regards,
Community Support Team _ Ailsa Tao

Status: Investigating

Hi @ybarsabal ,

 

I don't quite understand your problem,  It would be great to have a detailed picture to describe your problem. Since this is a public community, please be careful not to include sensitive information.

 

Best regards.
Community Support Team_Caitlyn

  • Report Server
Status: Delivered

Hi all,

 

This issue has been fixed, thanks for your patience!

 

Best regards.
Community Support Team_Caitlyn

 

Status: Accepted

Hi @chang_B 

It’s a known issue . The engineers are actively working on this issue and I will come back with an update if there is any progress.

 

Best Regards,
Community Support Team _ Ailsa Tao

  • Report Server
Status: Delivered

Hi  @vckbx 

I am so glad to hear that your issue has been fixed . I will change the status to "Delivered" .   

 

Best Regards,
Community Support Team _ Ailsa Tao

  • Report Server
Status: Investigating

Hi @BRNS 

It sounds like you are trying to refresh a Power BI dataset that includes a calculated table that depends on another table that uses Direct Query mode to connect to an Analysis Services data source. Unfortunately, Power BI does not currently support refreshing datasets that include calculated tables that depend on tables using Direct Query mode.

One solution you could consider is to change the source data for the calculated table so that it does not use Direct Query mode. This would allow you to refresh the dataset, but you would need to find a way to incorporate the data from the Direct Query source into the calculated table using other means, such as using Power Query to merge or append the data.

Another option is to use a separate dataset for the calculated table, and then use a measure or a report-level filter to control the data displayed in the report based on the data in the calculated table. This would allow you to refresh the main dataset without affecting the calculated table.

It's also worth noting that Power BI recently introduced the ability to refresh datasets that include calculated columns, so you may want to consider using calculated columns instead of a calculated table if that meets your needs.

 

Best Regards,
Community Support Team _ Ailsa Tao

Status: Delivered
  • Report Server
Status: Delivered

Hi @venuswang 

The issue has been fixed. Please have a check.

 

Best Regards,
Community Support Team _ Ailsa Tao

Status: Accepted
Status: Investigating

Hi @gp10 ,

 

We've found feedback from other users who have had similar experiences to yours. Here are some suggestions from the PG team Please see if this mitigates your problem.

"Customer appears to be using Feb 2023 version of the gateway. Can you please ask the customer to upgrade gateway to the latest version and re-capture gateway logs? There were some changes in the token refresh implementation in Jan 2023, upgrading will assure we have the latest version being used. Also ensure only one version of the gateway is installed.

 

Customer should also consider removing all existing credentials to the dataflow and recreating them. Sometimes that can fix authentication problems in PBI service."

 

Best regards.
Community Support Team_ Caitlyn

  • Report Server
Status: Accepted

Existing ICM for similar issue(ICM 297756751). It should be a new known issue that dataflow refresh taking long times that usual to complete. Employee engages this issue as well.

Status: Accepted

Hi @TiCordeiro 

This issue has been submitted to ICM , the ID is 343344031 . If there is any progress, I will come back to update .

 

Best Regards,
Community Support Team _ Ailsa Tao

Status: Delivered

Hi @SanilMaru 

PG is working on fixing this issue. Should be 3 - 4 weeks for the fix to be in production . Please wait patiently .

 

Best Regards,
Community Support Team _ Ailsa Tao

Status: Investigating

Hi @sgrewal 

Power BI Desktop has no login restrictions for external tenants. The only restriction is when it comes to sharing. Internal users are not allowed to share content directly from within the organization to external users, and there is no distinction between inside and outside the organization when logging into PBI Desktop or PBI Service. Unless your company's network security guidelines restrict the use of other domains.

 

I was able to log in to PBI Desktop using the two accounts in the screenshot, obviously they are not part of the same organization.

vyetao1msft_0-1685500748361.png

Best Regards,
Community Support Team _ Ailsa Tao

Status: Delivered

Thank you for sharing, for other users with similar experiences you can check the comments below. This thread will now be closed.

 

Best regards.
Community Support Team_ Caitlyn

Status: Accepted

Currently it have been considered as a known issue which would be fixed in early of September, so please stay tuned.

 

Best Regards,
Community Support Team _ Yingjie Li

Idea Statuses