Cell-level and range locking within an active scenario

Started by Marcus Delacroix · 1 year, 2 months ago · 3 replies · 3 views
Marcus Delacroix Participant
1 year, 2 months ago

Current lock granularity is at the scenario level. I'd like to lock individual cells or row ranges within an active planning scenario — for example, lock Q1 as closed while leaving Q2-Q4 open. This is a common FP&A workflow pattern.

3 Replies
Budget & Forecast Analyst · IberiaFin · 1 year, 3 months ago

For our monthly reforecast, we always want closed months to be read-only within the active scenario. The current approach requires scenario duplication just to enforce this, which creates version overhead.

Microsoft Fabric Consultant · CloudBridge Solutions · 1 year, 3 months ago

Logged as a known request. The time extension feature partially addresses this but doesn't cover arbitrary range locking within a scenario. I'll pass this thread to the product team.

Head of Financial Planning & Analysis · Nexa Retail Group · 1 year, 3 months ago

This would be a high-impact feature for rolling forecast management. We currently work around it with separate scenarios for closed vs open periods, but native cell/range locking would be much cleaner.

Viewing 3 replies - 1 through 3 (of 3 total)

Enterprise planning, Integrated with PowerTable and Intelligence, native to Microsoft Fabric. Co Engineered with Lumel.
BUILT ON