Microsoft PL-300 Bundle

COLLAPSE can reference a higher visual hierarchy level in a calculation. It serves “percent of parent category within a visible hierarchy”, not “KPI formula in every report and email subscription”.

Visual calculations are report-level computations and have export limitations. That matters for “calculation's result to appear in exported underlying data” rather than the condition “KPI formula in every report and email subscription”.

A narrative can describe selected visual content but must be validated. The boundary it addresses is “of the current page based on selected visuals”, while this case concerns “KPI formula in every report and email subscription”.

Bookmark capture reflects a state when saved, not every future change automatically. The boundary it addresses is “finds the bookmark does not preserve intended values”, while this case concerns “and a detailed table on the same page”.

Bookmark navigators expose saved author states as selectable navigation items. This solves “navigation pane needs to show all saved views”; the stated issue is “and a detailed table on the same page”.

Personal bookmarks capture an individual's report exploration state. Its application is “of slicers and sort order for later visits”, not the need “and a detailed table on the same page”.

Bookmark capture reflects a state when saved, not every future change automatically. Its application is “finds the bookmark does not preserve intended values”, not the need “of slicers and sort order for later visits”.

Bookmark navigators expose saved author states as selectable navigation items. That is a different operating condition from “of slicers and sort order for later visits”: “navigation pane needs to show all saved views”.

Bookmarks can capture author-defined display states for navigation. It serves “and a detailed table on the same page”, not “of slicers and sort order for later visits”.

Bookmarks can capture author-defined display states for navigation. That matters for “and a detailed table on the same page” rather than the condition “finds the bookmark does not preserve intended values”.

Bookmark navigators expose saved author states as selectable navigation items. The boundary it addresses is “navigation pane needs to show all saved views”, while this case concerns “finds the bookmark does not preserve intended values”.

Personal bookmarks capture an individual's report exploration state. This solves “of slicers and sort order for later visits”; the stated issue is “finds the bookmark does not preserve intended values”.

Bookmark capture reflects a state when saved, not every future change automatically. This solves “finds the bookmark does not preserve intended values”; the stated issue is “navigation pane needs to show all saved views”.

Personal bookmarks capture an individual's report exploration state. The deciding difference is “of slicers and sort order for later visits” versus “navigation pane needs to show all saved views”.

Bookmarks change presentation and cannot enforce data confidentiality. Its application is “report states, not merely hidden by bookmark selection”, not the need “navigation pane needs to show all saved views”.

Personal bookmarks capture an individual's report exploration state. It serves “of slicers and sort order for later visits”, not “report states, not merely hidden by bookmark selection”.

Bookmark navigators expose saved author states as selectable navigation items. The present requirement is “report states, not merely hidden by bookmark selection”; “navigation pane needs to show all saved views” is a distinct situation.

Bookmark capture reflects a state when saved, not every future change automatically. That matters for “finds the bookmark does not preserve intended values” rather than the condition “report states, not merely hidden by bookmark selection”.

Replace the technical field with appropriate user-facing descriptive attributes. That matters for “raw numeric ID instead of a meaningful ProductName” rather than the condition “Create a report-page tooltip linked to the Product”.

Hover context must flow to the tooltip to scope the displayed measures. The boundary it addresses is “shows all products rather than the hovered one”, while this case concerns “Create a report-page tooltip linked to the Product”.

Simplify tooltip content and ensure primary information remains available without hover. The deciding difference is “it obscures most of a mobile report” versus “Create a report-page tooltip linked to the Product”.

Hover context must flow to the tooltip to scope the displayed measures. The deciding difference is “shows all products rather than the hovered one” versus “Add a descriptive tooltip explaining the KPI definition”.

Report-page tooltips can show multiple supporting visuals in the hovered context. Its application is “Create a report-page tooltip linked to the Product”, not the need “Add a descriptive tooltip explaining the KPI definition”.

Simplify tooltip content and ensure primary information remains available without hover. That is a different operating condition from “Add a descriptive tooltip explaining the KPI definition”: “it obscures most of a mobile report”.

Report-page tooltips can show multiple supporting visuals in the hovered context. The present requirement is “shows all products rather than the hovered one”; “Create a report-page tooltip linked to the Product” is a distinct situation.

Tooltips reveal concise secondary details without cluttering the page. That matters for “Add a descriptive tooltip explaining the KPI definition” rather than the condition “shows all products rather than the hovered one”.

Simplify tooltip content and ensure primary information remains available without hover. The boundary it addresses is “it obscures most of a mobile report”, while this case concerns “shows all products rather than the hovered one”.

Hover context must flow to the tooltip to scope the displayed measures. The boundary it addresses is “shows all products rather than the hovered one”, while this case concerns “it obscures most of a mobile report”.

Report-page tooltips can show multiple supporting visuals in the hovered context. This solves “Create a report-page tooltip linked to the Product”; the stated issue is “it obscures most of a mobile report”.

Replace the technical field with appropriate user-facing descriptive attributes. Its application is “raw numeric ID instead of a meaningful ProductName”, not the need “it obscures most of a mobile report”.

Simplify tooltip content and ensure primary information remains available without hover. Its application is “it obscures most of a mobile report”, not the need “raw numeric ID instead of a meaningful ProductName”.

Report-page tooltips can show multiple supporting visuals in the hovered context. That is a different operating condition from “raw numeric ID instead of a meaningful ProductName”: “Create a report-page tooltip linked to the Product”.

Hover context must flow to the tooltip to scope the displayed measures. It serves “shows all products rather than the hovered one”, not “raw numeric ID instead of a meaningful ProductName”.