Dropdown Slicer

[RonanSmyth]

Hi there,

I'm using a dropdown slicer to filter on customer name. This works fine in desktop but throws an error when published to service.

The data is coming from a number of database tables. The gateways are working fine.

In service the visual greys out and displays the message:
An exception occured due to an on premise service issue.

Error fetching data for this visual

Couldn't retrieve the data for this visual. Please try again later.

Please try again later or contact support. If you contact support, please provide these details

Activity ID: 8614548b-5bb5-49a0-bec1-4a191292ea99
Request ID: 10c298d2-3fc9-470b-bf65-8f9f6779d0d9
Correlation ID: 4892d975-59a4-f822-7af9-b903c1c7eea2
Time: Thu May 22 2025 10:48:58 GMT+0100 (British Summer Time)
Service version: 13.0.25918.43
Client version: 2505.2.24206-train
Cluster URI: https://wabi-uk-south-c-primary-redirect.analysis.windows.net/

Any help would be much appreciated.

Thanks

Ronan

[v-achippa]

Hi @RonanSmyth,

Thank you for reaching out to Microsoft Fabric Community.

The issue here is most likely related to the on premises data gateway configuration or the unsupported query transformations used for the Customer Name dropdown slicer.

• Verify that your On-premises Data Gateway is online and all the connected data sources show a green check mark. If not reconfigure or restart the gateway service.
• Confirm that the data source credentials are correctly configured and updated and the privacy levels are compatible in the service.
• Simplify the power query steps for the Customer Name field to ensure query folding is supported. 
• For now try using a basic slicer or convert the dropdown to a list slicer to check for any UI timeout issues.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @RonanSmyth,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @RonanSmyth,

We wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @RonanSmyth,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[RonanSmyth]

Hi @v-achippa 

No, this was not the solution.

While I appreciate that not everyone reads the documentation before posting here, I assure you that I posted after reading the documentation and confirming that the issue was deeper than that. 

I think that the specifics of what I said in the OP have been largely ignored. I stated that the gateways were fine so there wasn't any need for the suggestion about checking gateways. 
Furthermore, I outlined how the slicer works in desktop and not in service which I feel has not been addressed. 

What I didn't mention in the OP was that the same slicer logic worked in other pages of the same report. It all uses the same gateway, same relationships and the page itself resembles other pages so much that, as a data analytics professional, I have determined that this really has all the trademarks of a known internal PBI bug. 

Being a subscriber of PBI pro, my organisation does not qualify for customer service, which is a foreign concept to me. So I pasted the support details here as I had seen in other posts that support staff often provided solutions. 

Thanks for your interest but the issue persists.

Ronan

[v-achippa · Accepted solution]

Hi @RonanSmyth,

Here the slicer working in the desktop. The same slicer logic works on other pages of the same report, the relationships and gateway are consistent. This could be a power bi service rendering or cache related bug, possibly specific to that page, visual or data volume. So I request you to please raise a support ticket in the Microsoft Fabric Community Forum.

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @RonanSmyth,

As we haven’t heard back from you, we are closing this thread for now. If you have any further issue, please raise a new thread in the community forum, we are ready to assist you on it.

Thank you for being part of Microsoft Fabric Community.

Thanks and regards,

Anjan Kumar Chippa

[RonanSmyth]

Hi Deku,

It's not a custom visual.

Thanks

[Deku]

Is this a custom visual? Has it been approved for use in tenent admin settings?