The local rehearsal separates North baseline four from South exploration six. Exit show restores North. A frozen R1 North record stays four when the supplied R2 scenario changes the live North total to five. This is a state-model demonstration, not a Power BI add-in or a connected report.
Work through the example
Select Present South to display six during the illustrative slide show. Exit show restores the North baseline at four. Select Freeze North R1, then Supply R2. The displayed frozen view and retained record remain R1 North four. Select Live view to see the local live North total of five at R2; the frozen record still remains four. Its value comes from a captured fixture state, not an actual PowerPoint snapshot.
Record mode, selected region and source revision at every rehearsal checkpoint. A frozen view and live view may represent different valid revisions. R2 supplies a changed North total but no category split, so do not invent that split. Test the named Snapshot and Public snapshot audiences in the native environment, keeping source refresh separate from add-in reload and displayed values.
Confirm the native add-in workflow
Microsoft describes an add-in for report pages and individual visuals, with Office build, account, license/capacity, and organizational requirements. Confirm the Office build, account, license or capacity, and organizational requirements before preparing the slide. Power BI add-in requirements.
The documented Embed live data export route remains service-connected; it does not move the underlying dataset into the PowerPoint file. Keep that distinction when choosing the native report-page or visual link. Add live Power BI data.
When setting up the add-in, record the service URL, page and visual IDs, Office build, tenant settings, account, licensing/capacity and viewer access.
Use a small fictional Counts fixture
Use this fictional specification for report page Counts, visual V01, source revision R1 and presentation slide S01:
| Region | Category A | Category B | Total |
|---|---|---|---|
| North | 3 | 1 | 4 |
| South | 2 | 4 | 6 |
These supplied counts are fictional. Their arithmetic provides a recognizable state marker: North displays 4, South displays 6. It is not actual business reporting or observed service data.
Keep the proposed report source, slide mapping, filter baseline, and rehearsal ledger together. The expected values help identify which view an observation belongs to, but they cannot prove the add-in has loaded.
Set and test the edit-mode baseline
Microsoft documents saved edit-mode selections and unsaved slide-show selections, with exit restoring the prior edit state. Its Snapshot is report-access controlled; Public snapshot is visible to deck viewers. Live restoration reloads service data, while Refresh does not retrieve upstream source data. Snapshot switching is a desktop feature. Present and snapshot behavior.
For the original fixture, set the intended baseline to North while preparing S01. Design this native rehearsal:
| Checkpoint | Expected fixture marker | Actual observation |
|---|---|---|
| Prepared edit view | North, R1 total 4 | Pending |
| Slide-show exploration | South, R1 total 6 | Pending |
| After leaving the show | North baseline | Pending |
Keep the filter state and the data revision separate. The final row checks the baseline, not a promise that a later service revision still contains the same total. Record actual mode, filter, visual, source revision, and time at every checkpoint.
If the presenter wants South to be the next starting view, prepare and verify a new baseline as its own revision. A temporary exploration should not silently rewrite the rehearsal record.
Label the frozen view and service revision
Plan a frozen North view at R1, total 4. Then supply a separate fictional R2 scenario in which North's total is 5 after a separately confirmed native model/service refresh. The exact changed row must be documented in the later R2 fixture; this article does not invent one.
Recreate this example
Build one self-contained responsive HTML example titled “Power BI in PowerPoint: rehearse state and revision” for readers completing the stated task. Return the complete HTML with embedded CSS and JavaScript. Use no remote fonts, libraries, images, requests, account connections, or saved-state claims.
Use fictional Counts page, visual V01, slide S01, source R1: North A=3, B=1, total=4; South A=2, B=4, total=6. Provide Present South, Exit show, Freeze North R1, Supply R2 and Live view buttons. Baseline is North; presentation exploration shows South total 6 and exit restores North. Freeze records R1 North total 4. Supply R2 changes only the live North total to 5, without an invented category breakdown, and keeps the displayed frozen view at 4. Selecting Live view then displays North R2 total 5 while the frozen record stays 4. Show mode/filter/revision separately and explicit native-add-in-unverified label. Include access distinctions Snapshot report-authorized, Public snapshot deck viewers without report permission grant. No permission change, refresh request, native slide or service connection.
Use a presentation rehearsal board with filter totals, frozen-state record and source revision labels design with a compact header. Keep the actual sample data, controls, and useful default result visible early on a 360px-wide screen. Use readable text at least 16px, generous paragraph spacing, strong contrast, semantic labels, visible keyboard focus, and wrapping source blocks. Stack records on narrow screens rather than forcing a wide table.
Wire each action to an explicit type=button click handler using element selectors; the host permits scripts but blocks form submission. Update the visible result when the described action occurs. Show specific error feedback for invalid or missing input and clear stale feedback after dependent inputs change. Use plain text when displaying user values.
The local rehearsal is not Power BI, PowerPoint, a real snapshot or a report-access test. Keep the source fixture and worked teacher or developer example distinct from actual user records. Include the domain-specific explanation and next check beside the result. Provide no fake download, send, deployment, approval, or persistence button. Everything operates locally for the current page session.
Review the prepared copy in NOS
Before presenting, confirm the opening filter, intended data revision and named snapshot audience in the actual add-in. A sanitized HTML rehearsal ledger in NOS can support visual edits to eligible static presenter notes. Keep the PowerPoint file, report and actual access observations in their authorized workflow.