Forum Discussion
Copilot Narrative + Bookmarks
- 19 days ago
rohit1991 Thank you, I agree with using the horizontal Page Navigator.
My current thinking is:
- Keep only Overview and Detail as bookmark states/pages.
- Add a short summary narrative on the Overview page.
- Create a dedicated Analysis page for the full report narrative.
My question is around how the Copilot Narrative determines what to analyse.
If the Analysis page is configured to generate a report-level story, how does it reference visuals on the Overview and Detail pages? Do I explicitly select the visuals across pages and bookmarks for the Narrative visual, or can it analyse content exposed through bookmark states?
For example, if a visual is hidden by default and only becomes visible through a bookmark, or if slicers and filters change the view, will the narrative include those insights after refresh? Or does it only use the explicitly selected visuals regardless of bookmark state?
I'm trying to understand the recommended design pattern:
- Narrative per bookmark/view plus a final summary page, or
- A single Analysis page that can generate a complete story across all relevant visuals, bookmark states, and filter context.
Sorry i am lost, what is best analyeses per page or across all pages or per bookmark "im not sure about the state being in sybc with the slicing and visiblity making it updated" becuase then i rather move the detail bookmark to a page and keep slicers in sync?
- 19 days ago
Hii icassiem
The best design is to use Overview and Detail as separate pages, sync the required slicers, and keep a dedicated Analysis page with a report-level Copilot Narrative. Configure the narrative to include the required pages or visuals explicitly. Do not rely on bookmark-hidden visuals, because Copilot uses the data visualized by the selected and available visuals not every stored bookmark state. After slicers or filters change, users must select Refresh on the narrative to regenerate it with the current context.
Hi icassiem,
You're welcome!
Yes. According to the Power BI March 2026 Feature Summary, instead of clicking Refresh every time you select a slicer in a report with the AI Narrative visual, you can use the Auto refresh toggle in the Visualizations pane. Microsoft states that this "enables the summary to update automatically whenever a slicer selection changes," creating a smoother and more efficient reporting experience.
For more details, please refer to the following official Microsoft resources:
Power BI March 2026 Feature Summary - Microsoft Fabric Community
Create a Narrative Visual With Copilot for Power BI - Power BI | Microsoft Learn
I hope this helps!
v-abhinavmu Thank You.
2 last ques, you mentioned previsously a refresh button, i think there a slcier reset botton? but is there a narratvive visual refresh button for users too?
- v-abhinavmu13 days agoCommunity Support
Hi icassiem,
You're welcome!
Yes. According to the Microsoft Learn documentation, the Narrative visual includes a Refresh button. When users apply slicers or filters, the narrative doesn't automatically update. Instead, users can use the Refresh button to fetch an updated summary based on the applied slicers and filters.
Additionally, the Power BI March 2026 Feature Summary introduced an Auto refresh option for the AI Narrative visual. Microsoft states that instead of clicking Refresh every time, you can use the Auto refresh toggle, which "enables the summary to update automatically whenever a slicer selection changes."
I've attached the relevant screenshots from the official Microsoft documentation for reference.I hope this helps! Please let us know if you have any further questions.