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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Smart Narrative not working when viewed in Service

Suddenly Smart Narratives in PowerBI Service is not working. The smart narratives work correctly in Desktop and were previously working in service when published through the app. I get an error now that says " the smart narratives is not supported". This issue is happening on multiple reports across multiple organisations that I have published to.

 

@av9 @CaronTurner @Anonymous 

Status: New
Comments
mike_honey
Memorable Member
srinivt
Employee

Thanks for reporting this issue. This is a regression and we are currently in the process of rolling out a fix very soon.

v-chuncz-msft
Community Support

@jerome1689 

 

A similar issue has been reported internally, so stay tuned.

CRI 246723182

SeanMcLarty
Advocate I

Smart Narriative seem to be working again.  Phew, I had some half-yearly reports about to kick-off.

kelseyrondini
New Member

@srinivt - any updates on this? We are still experiencing the issue on our published dashboards.

srinivt
Employee

The issue was addressed early last week itself. However, some users are still seeing the error because of caching in browser. Please clear your browser caches or open a new incognito browser window & try again. You can also try to apply a new filter which will likely not hit the cache, then you should see your smart narrative textbox working. 

kelseyrondini
New Member

@srinivt , I've cleared my cache, applied a new filter, and used a new browser. Still experiencing the issue. It looks like the issue resolves for a moment, but when I navigate to a different report page and return the issue is back.

kelseyrondini
New Member

@srinivt , scratch that - looks like the filter tip works. I applied a completely unrelated filter (index < 10), published, removed filter, published again, and that resolved it! Thanks very much.