Webinars 
Fabric Planning (PowerTable): Extending Planning Models with Forward-Looking Reference Data
Recorded Tue, Aug 18, 2026
57 minutes

Fabric Planning (PowerTable): Extending Planning Models with Forward-Looking Reference Data

A plan built only on historical fact data can't show new products, new segments or future periods, and it can't hide combinations you no longer plan for. This session shows how to add a few planning fields and a validity (bridge) table to your dimensions, maintain them in PowerTable, and use simple DAX measures so planning sheets pick up the changes automatically. It ends with live Q&A.

Key takeaways

  1. The fact table defines the grid, and that is the problem. A semantic model only shows combinations that already have transactions. New products, segments and territories stay invisible until they transact, and discontinued ones keep showing up as stale rows.
  2. Two calendar fields make the forecast window dynamic. Adding "Is Valid for Forecast" and "Date Is Open" to the date table, with measures for open status and forecast begin and end dates, forces future periods onto the grid. Filtering the sheet on the forecast flag instead of a hard-coded year means it rolls forward when the business opens new months.
  3. A validity flag on a dimension adds and removes members. An "Is Valid" column on the segment table, plus a measure that returns revenue or zero for valid segments and blank for invalid ones, brings a new segment onto the grid and drops retired ones without touching the semantic model.
  4. A bridge table handles multi-dimensional combinations. For country and product, a bridge table lists which combinations are open for planning. Measures filter revenue by the valid rows, so a new product line can be planned in one country only while other countries and regions drop out.
  5. Lock closed periods from the data, not the sheet. The planning sheet can set open and closed periods in its modeling settings, but then someone has to edit the sheet at each close. Setting the input measure's allow-input rule to a formula on "Date Is Open" lets the reference data decide.
  6. Business users maintain the reference data in PowerTable, with governance. PowerTable sits on a Fabric SQL database. Access settings control who can add, edit or delete rows and which columns they can change. Approvals run up to three levels, with Submit for Review and a Microsoft Teams notification to the approver, and every data and configuration change is audited.
  7. The demo architecture is simple to copy. Actuals sit in a Fabric lakehouse, dimension tables sit in Fabric SQL managed by PowerTable, OneLake shortcuts bring the SQL tables into the lakehouse, and a Direct Lake on OneLake semantic model sits on top. New products get a surrogate key so they can exist before the ERP assigns a SKU.

FAQ

  • When I add a column in PowerTable, is it stored in the SQL database or in the original date dimension in the lakehouse?
    In the Fabric SQL database. In this setup the dimension tables live in Fabric SQL and appear in the lakehouse as OneLake shortcuts, so data is referenced in place rather than copied. After a schema change such as a new column, refresh the SQL analytics endpoint and the semantic model so the new field shows up.
  • Our budget is in a spreadsheet already connected to the semantic model. How do we replace it with Fabric Plan?
    There is no one-step conversion of a spreadsheet and its logic. Make sure the data the spreadsheet uses is in Fabric, in the lakehouse or Fabric SQL. A planning sheet is built on a semantic model, so reuse your existing model if you have one, or build a basic one with your fact and dimension tables. Then recreate the plan on top of it.
  • How do you apply advanced forecasting rules to the forecast period?
    Use a mix of the input measure's built-in settings and DAX. Input measures support rules such as minimum and maximum values and default values, and can run formulas when values change. More complex logic can be written in DAX in the semantic model.
  • With a daily calendar, isn't it hard to mark every day valid or open?
    Use a PowerTable automation rather than editing each day by hand. For example, an automation can open or close every day in a selected month in one action.
  • How does a new product added for planning match up with the ERP once it goes live?
    The demo uses a surrogate key in PowerTable so new products can be created before they have a SKU. Once the ERP assigns the SKU, someone enters it on the PowerTable row, or the load process matches the new record by name. Either way, one side has to be told the new identifier.
  • Is Fabric Planning, and PowerTable in particular, charged per user, per query, or some other way?
    Per user, through sessions under activity-based licensing, billed on your Fabric capacity. A session lasts 30 days, and its session type depends on what the user does: viewing is a Viewer session, editing or maintaining data is a Stakeholder session, and authoring a planning sheet is a Planner session. Authoring tables in PowerTable stays at Stakeholder. If a user doesn't use Fabric Plan in a later month, there is no charge for them that month.

Resources

Speakers
Eric Hood Director - COE, Lumel
PRESENTATION DECK

Webinar slides

PDF

Sign in to download the slides. Community membership is free.
Microsoft, Azure, Copilot, Excel, Fabric IQ, Microsoft Entra, Microsoft Fabric, Microsoft Teams, OneLake, Outlook, Power Automate, Power BI and SharePoint are trademarks of the Microsoft group of companies. IBCS is a registered trademark of IBCS Association. All other trademarks are the property of their respective owners.

This community is operated independently by Lumel. Nothing on this site constitutes a representation or warranty by Microsoft.