Cross highlight issue

Hi difolt ,

By my tests, I could reproduce your issue.

I have reported this issue internally and will update here if I get any information.

Best  Regards,

Cherry

Hi difolt ,

Update:

By my tests, I'm afraid that your issue may caused by the row fileds are from different tables.

Confirmed by PG, this is by design. We currently do not support filtering of Measures using multiple fields from different tables. Error message is confusing and we'll look into ways of improving and better documenting this.

Best  Regards,

Cherry

Hi v-piga-msft ,

Unfortunately, this error still exists when you choose two different levels from different tables. 

Do you have any updates from PG?

Thank you in advance for the information.

Proud to be a Super User. If I helped, please accept the solution and give kudos!  Linkedin

Following

Hi, It seems this issue still remains unresolved. I am getting the same error, with same text message in 2022. At first, it is itself confusing which measure and visual is troubling?

This issue still exists as of today in the May 2023 GA release of Power BI Report Server.  I can also confirm that it affects both stacked column and ribbon charts displaying a total revenue number (measure) that is filtered by both the legend category in the visual (i.e. the stack categories) and the fiscal year on the X axis.  These are two separate dimensions in the data model and do NOT represent two different levels of the same hierarchy. 

If I select a legend value in one chart and a fiscal year value in another chart on the same page, it works fine, even though the fiscal year in both charts comes from the same dimension.

I can also add that I do not have this problem with a different stacked column/ribbon chart that uses a value from the fact table as the stacked category and the same fiscal year dimension as the chart with the problem.

I am reasonably certain that this was not an issue at some point in the past, as I have reports dating back to Fall 2017 that I have never seen this behavior in but are now experiencing the error.