From: Rowan Chen, Digital Sales Lead
Use the fictional web_orders_2026.csv file. Normalize Channel from Store to In-store. Load it as Web Orders, connect Store names to the existing Store dimension, and create a 2026 calendar. I need online sales and order volume by region and month, a channel selector, regional drill-through detail and a Back button. Define Web East access on Store and test it. Finish with a captured Performance Analyzer baseline. Desktop authoring and testing happen here; publishing and assigning real users happen in the service.
The digital sales team has sent a new January 2026 order file. Take it through import, a small cleanup, a model relationship and a report with security. The file is separate from the earlier 2024 and 2025 Sales table, so don't accidentally point a new measure at the old facts or use a calendar that stops before the new orders.
Each step carries your work forward. Normalize the source labels, load the table, connect its stores and build a calendar that covers the file. Then create reusable measures and add an overview with a drill-through detail. The last steps define and test a regional role and capture estimated performance. The deliverable is a working report model ready for a controlled publishing process, with its access test and timing limits stated.