Rogue valid character error

[kerryleaab]

I'm getting a "error fetching data for the visual" error because "the code point does not correspond to a valid character". This only applies to one slicer and if I turn that slicer into a table visual it works without issue. I'm also using the field in numerous reports without issue. This makes me think the error isn't actually to do with valid characters because how could it work as a table but not a slicer.

Wondering if anyone has seen this before and/or knows how I can try to fix it please?

[etalon]

FYI I got this same error when I was filtering a slicer on a direct queried in powerbi dataset that contained text including a emoji!!
Remove the emoji, and the error went away.

[v-saisrao-msft]

Hi @kerryleaab ,

Please provide sample data or Pbix file that covers your issue or question completely, in a usable format (not as a screenshot).
Do not include sensitive information. Do not include anything that is unrelated to the issue or question.
Please show the expected outcome based on the sample data you provided.

Need help uploading data? 

https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...
https://community.fabric.microsoft.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447...

Thyank you.

[kerryleaab]

Hi @v-saisrao-msft thanks for your response - I tried using sample data but can't seem to recreate the issue. Unfortunately the issue is occuring with confidential data so cannot share. I am working on a workaround by using a different field as a filter.

[v-saisrao-msft · Accepted solution]

Hi @kerryleaab,

I wanted to check if the issue has been resolved, since you mentioned you were working on a workaround by using a different field filter for your issue.

Thank you.

[rajendraongole1]

Hi @kerryleaab - you can delete the slicer and re-add it to the report.Sometimes slicers retain cached filter states that become incompatible when underlying data slightly changes.Use a calculated column with UNICODE and also share the calculation that you used. hope this helps.

[kerryleaab]

Hi @rajendraongole1 thank you so much for your quick response! I have tried removing and re-adding the slicer but am still getting the same error message. The column I am filtering is a simple text column [accountname] with no additional calculations. If I create a calculated column for UNICODE([accountname]) there don't appear to be any errors.