Forum Discussion
Copilot Narrative + Bookmarks
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?
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.
Hii icassiem
For only 2-3 pages, use a horizontal Page Navigator at the top; it is resizable and does not need to occupy the full left column. Keep Overview/Detail/Analysis in a separate Bookmark Navigator group.
For the Copilot Narrative, explicitly select the pages or visuals it should summarize. It only uses data visualized by those selected visuals, so do not rely on bookmark-hidden visuals being included automatically. After filters or bookmark states change, users must refresh the narrative. Use the narrative visual’s own prompt for instructions the Copilot pane is a separate experience.
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?
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.
rohit1991 Thank You so much, this is clear becuase the AI narrative is a real pluss in a consulting orgnization and i needed to ensure my enterprise layout is diffwrent. maybe not overview and detail maybe call it spefic stories but have sections or dill downs to detail etc. So will keep bookmarks for visuals i alrady have covered for the AI