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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Share your ideas and vote for future features

0 Votes
Status: New
0 Votes
Status: New
0 Votes
Status: New
0 Votes
Status: New
0 Votes
Status: Investigating

Hi @Analyst-Rene ,

 

Are you using New slicer? Please provide details of the version of Power BI Desktop you are using and we will report this issue internally.

 

Best regards.

Community Support Team_Caitlyn

0 Votes
Status: Delivered

Hi @dmathewg ,

 

As you can see in the error message, it is not currently supported.
Direct Lake suits near-real-time scenarios similar to Import mode, but it does not handle real-time scenarios like DirectQuery.

As for titimeline when this will be available,the answer is no,You can stay tuned for more official announcements from Microsoft, thanks in advance!

 

Direct Lake vs. Import mode in Power BI - SQLBI

Best regards.
Community Support Team_Caitlyn

0 Votes
Status: Investigating

Hi @aschkan ,

 

We would like to confirm this further, do you mean that the German translation is incorrect after the renaming of the alarm here or that the renamed content is not displayed correctly?

 

Best regards.
Community Support Team_Caitlyn

Status: Delivered

Hi @mvgust 

So everything's back to normal now is it ? I will change the status to "Delivered" .

 

Best Regards,
Community Support Team _ Ailsa Tao

0 Votes
Status: Investigating

Hi @OlgaBlesa 

If you delete this report on Service and republish it, do you still have the same problem? Can this report be modified by anyone other than you? Did you set the bookmark in the report?

 

Best Regards,
Community Support Team _ Ailsa Tao

0 Votes
Status: New
0 Votes
Status: New
0 Votes
Status: Investigating

Hi @mmerchak ,

 

We would like to know more details about this issue,if you downgrade gateway version to older than Feb 2024. Currently supported monthly updates to the on-premises data gateways | Microsoft Learn

 

Will this problem persist?

Best regards.
Community Support Team_Caitlyn

0 Votes
Status: Investigating

Hi  @mrmossevig 

The problem seems to be with this published app, you can either go directly to the corresponding app to react to this situation, or you can just mention a Support ticket. 

Business Apps – Microsoft AppSource

You can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.

It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: https://powerbi.microsoft.com/en-us/support/

For how to create a support ticket, please refer to https://community.powerbi.com/t5/Community-Blog/How-to-create-a-support-ticket-in-Power-BI/ba-p/6830...

 

Best Regards,
Community Support Team _ Ailsa Tao

0 Votes
Status: Delivered

Hi @DENISJANITRA 

This issue will be fixed with the next version of PBI Desktop. Please be patient and wait for the version update, thank you for your cooperation !

 

Best Regards,

Community Support Team _ Ailsa Tao

0 Votes
Status: Delivered

Hi @JSmith912 ,

 

The default date format of the Power BI slicer depends on the client’s regional settings.

Even if you change the date format in Power BI Desktop, the date format may change according to the language setting of the browser when the report is published to the Power BI service. Therefore, if you want to see the same date format in the Power BI service as in Power BI Desktop, you may need to check and change the language setting of the browser. 

 

Solved: date format in slicer - Microsoft Fabric Community

Re: Date format in slicer is changing to mm/dd/yyy... - Microsoft Fabric Community

 

Best regards.
Community Support Team_Caitlyn

0 Votes
Status: Investigating

Hi @Element115 

You replaced the new LH, is this LH the same as the previous one? After you connect to the datasource, all the table names and column names of your datasource are the same? Then all the names in your report are not changed, but the slicer has a problem? After you remove the relevant fields and then re-add them, it's back to normal? Is the slicer you are talking about old or new slicer ? So other visual with the same fields will have a problem? 

 

Best Regards,
Community Support Team _ Ailsa Tao

0 Votes
Status: Investigating

Hi @spindive,

 

We saw that you opened a support ticket and the ticket engineer has higher access to investigate this issue than the community support engineer, I would like to know more about this ticket, did they inform you that this issue was acknowledged as a bug and reported internally?

 

Best regards.
Community Support Team_Caitlyn

0 Votes
Status: Investigating

Hi @zinchic ,

 

If you want to make Power BI interactive with Excel , it depends on whether you want to export the whole report or the data of a single visual object, you can check this documentation:

 

Export data from a Power BI visualization - Power BI | Microsoft Learn

Create Excel workbooks with refreshable Power BI data - Power BI | Microsoft Learn

 

Best regards.
Community Support Team_Caitlyn

0 Votes
Status: Investigating

Hi @Jerinfonterra ,

 

If scrolling the scroll axis to the right does it work for you? Have you tried resizing the page in Power BI Desktop?

vxiaoyanmsft_0-1713864864797.png

 

Best regards.
Community Support Team_Caitlyn

0 Votes
Status: Investigating

Hi @Lingaraj-Mishra ,

 

Certain tenant configurations in Azure AD could potentially restrict or alter the behavior of the client credentials grant. It's important to ensure that:

1.The application registration in Azure AD is correctly configured with the necessary API permissions for Power BI.

2.Admin consent has been granted for the permissions required by your application.

You may verify API Permissions,double-check that the API permissions assigned to your application in Azure AD include and that these permissions have been granted admin consent.Dataset.Read.All
Also ensure that the scope parameter in your token request is correctly set to . This scope is necessary for accessing Power BI REST APIs.https://analysis.windows.net/powerbi/api/.default
When making API requests with the obtained token, ensure that the header is correctly formatted as .AuthorizationBearer {token}
Look closely at the response from the token request. It may contain additional details or error codes that can help pinpoint the issue.Although you've mentioned verifying these, it's worth double-checking the application ID, secret, and tenant ID for any possible typos or mismatches.

 

 

For more information on authenticating with Power BI REST API, you might find the following documentation helpful: Authenticate with Power BI REST API

 

Best regards.
Community Support Team_Caitlyn

Idea Statuses