Built a full Revenue Planning app for 15 regions — here's how

Started by Priya Ramaswamy · 1 year, 3 months ago · 3 replies · 1 view

Priya Ramaswamy Participant

1 year, 3 months ago

After six months of work, our Revenue Planning app is live. We have 15 regional managers entering their monthly revenue targets, and two scenarios (Conservative and Stretch) alongside the locked baseline. The CFO reviews consolidated actuals vs plan in an Intelligence sheet with a waterfall chart. Key architectural decisions: (1) one semantic model, single source of truth, (2) Planning sheet per region with shared measures, (3) writeback to a single Fabric SQL table with region as a partition key. Happy to answer questions.

3 Replies

Sort

Marcus Delacroix

Senior BI Architect · Peak Logistics Europe · 1 year, 4 months ago

This is exactly the reference architecture I've been looking for. Did you use RLS on the Planning sheet to prevent regional managers from seeing each other's inputs, or did you keep it open during the planning cycle?

Up

0

Priya Ramaswamy

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

We used RLS inherited from the semantic model. Each regional manager can only see and edit their own region's rows. The consolidated view is restricted to the CFO and FP&A team roles. Worked beautifully.

Up

0

Sofia Martínez

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

Did you run into any performance issues with 15 concurrent planners writing back during peak budget season? We have a similar setup and I'm nervous about the writeback layer.

Up

0