Display issue with Cortana

[Anonymous]

I have a Cortana card on one of my reports, and up until a week ago it worked fine.  Now however, the standard filter visual appears to be showing up in "edit mode" instead of displaying the filter values:

 It seems like a a bug, but wanted to check and see if anyone knows what the problem is. 

[v-qiuyu-msft]

Hi @Anonymous,

I'm not able to reproduce the issue on my side. Please follow below below steps to troubleshoot the issue:

1. Open the troubleshooting tool by adding "/cortana/test" to the end of your Power BI service URL. Your URL should look similar to this: app.powerbi.com/cortana/test. Check if the slicer dispaly fine.

2. Make sure the report which has Cortana answer page is created by the latest Power BI desktop version 2.49.4831.521.

3. Verify the report in Power BI service isn't in Edit mode during the time you run the Cortana to search it.

4. Please try to test with our test pbix file to see if the same issue occurs.

Best Regards,
QiuyunYu

[Anonymous]

Thank you for your suggestions.

1.  /cortana/test produces the same issue.

2.  Confirmed - using latest version.

3.  Confirmed - PBI Service is not in edit mode.

4.  The test file you gave me is doing the same thing:

[v-qiuyu-msft]

Hi @Anonymous,

Please run the Fiddler with Decrypt HTTPS traffic enabled, then type the app.powerbi.com/cortana/test in browser to reproduce the issue, share .saz file with us.

Best Regards,
QiuyunYu

[Anonymous]

I'm not very familiar with Fiddler; wouldn't this .saz file have sensitive information in it since it's decrypting HTTPS?

I'm on a work computer so I'm hesitant to post the results.  Is there something in the file I should be looking for?

[v-qiuyu-msft]

Hi @Anonymous,

You can follow this article to capture the HTTPS traffic: http://docs.telerik.com/platform/knowledge-base/how-to/how-to-capture-fiddler-trace. Then share .saz file via Private Message.

Best Regards,
QiuyunYu

[Anonymous · Accepted solution]

Well, I'm not sure why, but as of yesterday the issue is gone.  I did not update anything or change anything...  so I'm at a loss to explain what the cause was.