FAQ

This FAQ addresses common questions and clarifications that arise while working with plan. It covers environment setup and interface navigation.

What permissions do I need to create a plan app?

You need Contributor or higher access to the Fabric workspace and at least Build access to the semantic model you want to connect.

Can I connect one plan app to multiple semantic models or change the semantic model after the plan app is created?

No — each plan app connects to one semantic model, and it cannot be changed once it is connected. If you need to plan against different data sources, you will have to create separate plan apps.

What happens if my semantic model is not visible in the connection dialog?

Ensure that you have at least Viewer access to the workspace where the semantic model is published — the semantic model doesn't need to live in the same Fabric workspace as your report or item, since it can be accessed across workspaces. Still, you do need at least viewer-level permissions on its host workspace to see it in the dialog. If it still doesn't appear, try refreshing the connection or signing out and back in.

As a contributor, can I create my own semantic model connection?

No, contributors cannot create a semantic model connection directly. If you only have contributor access, the workspace admin should create the connection, and the contributor can use it.

What is the Fabric SQL database used for?

The Fabric SQL database is where Fabric Planning stores all plan data — inputs, forecasts, scenarios, and writeback entries. It is separate from the semantic model so that plan data can be written back without affecting the underlying actuals or reporting layer.

What's the difference between the semantic model connection and the SQL database connection?

The semantic model connection pulls your actuals/reporting data in for planning, whereas the SQL database connection is a separate connection that enables collaboration — it's what allows the plan to be saved and shared and is set up after the planning sheet is built.

Can an existing connection be reused instead of creating a new one?

Yes. In the connection dropdown, an existing connection can be selected instead of choosing Create a new connection, provided it meets the prerequisites.

Does the plan app need to be created before or after the SQL database?

The SQL database is created first in this flow, but the two are independent items — creating one doesn't depend on the other. However, the SQL database should exist before writeback is attempted, since planning data can only be written back to a Fabric SQL database, not any other data source.

What is the difference between semantic model data and From Sheets data in the Data pane?

Semantic model data is read-only actuals and reference data pulled directly from your Power BI dataset — historical revenue, dates, and product hierarchies. From Sheets data is data created within Fabric Planning (forecasts, targets, sales plans) and made available for use in other sheets.

Can I add dimensions from different tables to the same planning sheet?

Yes — as long as the tables are related in the semantic model, you can combine dimensions from different tables in the rows, columns, and values of a single planning sheet. If the tables are not related, the values will not cross-filter correctly.

If I change the field assignments on a planning sheet - for example, moving a dimension out of Rows or removing a measure from Values — does it affect the underlying data?

No - field assignments are a display configuration only. Adding, removing, or rearranging what appears in Rows, Columns, and Values on a planning sheet does not alter the data in the semantic model or the Fabric SQL database. It only changes what is shown on that sheet.

What is the difference between a visual-level filter and a global filter?

A visual-level filter applies only to the current planning sheet and does not affect other sheets in the plan app. A global filter applies across all sheets.

How do I navigate a sheet with a large number of rows?

Use the footer's Settings control to configure how many rows are displayed per page, then use the page navigation controls - first, previous, next, and last - to move between pages. For columns that extend beyond the visible area, use the horizontal scrollbar at the bottom of the canvas or reduce the zoom level using the zoom slider in the footer. Collapsing the Explorer pane and sidebar panels also gives the canvas more space.

Can I export to PDF or CSV as well as Excel?

Yes - the Export dialog offers PDF, Excel, and CSV.

• PDF produces a fully formatted, paginated export preserving layout, cell values, number formatting, notes, filters, and calculated rows and columns. Advanced options let you configure page size, orientation, content order, scaling, margins, and whether to include comments, filter information, or a logo.

• Excel export is for further analysis and data manipulation, with three export modes: Fully Expanded (all hierarchy levels expanded flat), With Expand/Collapse (hierarchy grouping controls preserved in Excel), and Current State (exports exactly what's currently visible on screen, including applied filters and expanded levels).

• CSV is a flat data export useful for downstream processing, but it does not preserve hierarchy, formatting, or layout.

What actions can be performed and saved while in reading mode?

Viewing mode isn’t purely static. While it locks down the core design of your report, it keeps the planning sheet highly interactive for day-to-day work. However, there is a clear distinction between temporary visual changes and saved planning actions.

1. Temporary Actions (Not Saved)

You can customize your view on the fly by changing sheet layouts, updating number formatting, applying Top N rules, or filtering data. However, these visual adjustments are strictly temporary and will not be saved when you exit or refresh the report.

1. Saved Actions

The following core planning and data entry actions are fully saved and committed while working in viewing mode:

• Data Inputs: Type numbers directly into cells, as well as bulk edit, allocate, and distribute values across rows and columns.

• Forecasts: Change planning assumptions and distribute the updated impacts across your forecast columns.

• Comments: Add, update, and manage commentary.

• Writeback: Commits your data changes back to the backend database—provided an active writeback destination has already been configured by the report author.