Copilot Narrative + Bookmarks

[icassiem]

Good day,

I'm still designing a PBI report with Fabric F2 and would like to confirm a design enterprise approach before building it.

My planned layout follows this example use page navigator and bookmarks

1. Page Navigator, icons only on left to minimize width, if i only have 2-3 pages does it still take the entire column on the left. Is there a neater approach. I could move to the top with icons and have the bookmarks below foloowed by filters, just its to busy?

2. The Bookmarks (Overview tab, Detail tab, Analysis/Copilot tab)

The Analysis/Copilot tab would actually be a bookmark on the same report page. When selected, the bookmark would hide all charts and visuals and only show a Copilot Narrative visual that does the summary or analyses of the page

If the source visuals are hidden by the bookmark but still exist on the same page, will the Copilot Narrative visual still use them to generate insights and tell the story of the page? Or does it only analyze visuals that are currently visible? Or do i use the Copilot chatbot provide instruction based on the visual "but i have no clue what the state of visauls tabs are" to write pargagpah narrative analyses and keep the narrative visual at bottom of each tab?

I want to avoid building the Analysis/Copilot experience or false expectations this way if hidden visuals are excluded from the narrative context.

Please Help

Regards

[icassiem · Accepted solution]

@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?

[DataTako]

On the navigator: it only takes the space you give it. The page navigator is a single visual you resize, so with 2-3 pages you can shrink it to just the icons instead of letting it fill the column. With that few pages I'd put it horizontally along the top, icons only, and drop the left rail entirely. Keep filters in a collapsible pane so the canvas doesn't feel busy.

On the bookmark plus Copilot narrative: I wouldn't build it the way you've described. Hiding the source visuals with a bookmark and expecting the narrative to still read them is unreliable. Hidden visuals aren't guaranteed to feed the narrative's context, and this is exactly the spot where the Copilot narrative behaves inconsistently. You'd risk building the false-expectations experience you're trying to avoid.

Cleaner approach: make the Analysis/Copilot view a real separate page rather than a same-page bookmark toggle. The narrative then sits with its source visuals actually present and rendered, which is what it needs to summarise them reliably. If you want it visually clean, keep those visuals on that page but small or grouped, with the narrative as the hero. Either way, test it on your F2 with a couple of visuals before committing the whole layout, since this behaviour is worth confirming on your own tenant.

[icassiem]

@DataTako Thank You

1. Keep filters in a collapsible pane so the canvas doesn't feel busy - do yoiu have an example?

2. I was looking to provide a summary on page at the bottom, but yes pages only and the last page = analyses page of full report analyses narrative of all its pages with sliced "sync" content or must i repeat the visuals in the analyses page - it feels duplicated then im better off making a panel at the end of pages?

[rohit1991]

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.

[icassiem · Accepted solution]

@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?

[rohit1991 · Accepted solution]

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.

[icassiem]

@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