[Part 10] From demo to customer project [Fabric App]
At the end of this part you have a checklist of what to clarify before you promise a customer a Fabric App, and a list of what our demo deliberately …
At the end of this part you have a checklist of what to clarify before you promise a customer a Fabric App, and a list of what our demo deliberately …
At the end of this part every visual in the app follows IBCS notation: actuals solid, prior year light grey, forecasts hatched, labeled columns instead of a line, variances as …
At the end of this part you have changed a chart yourself: the line chart from Part 6 becomes a column chart. No prompt, no AI. – Today your AI …
At the end of this part your team plans in shared scenarios: approve a Base forecast, copy it, re-plan in the copy and compare both side by side. Time: about …
In the end of this part your users type forecast values into the grid, click Save, and the values come back after a refresh, stored in the app’s own database …
At the end of this part you have a Fabric app that shows live numbers from your semantic model: KPI cards, a monthly chart and a forecast grid per region …
At the end of this part you have a published demo model with a date table and eleven KPI measures, written by AI from exact „coordinates“ and checked against known …
At the end of this part you have Node.js, VS Code, Git and GitHub Copilot installed, both tenant settings enabled, and a first empty app running in Fabric. Time: 45–60 …
Co-author and co-learner: Claude (Anthropic). Reading time about 7 minutes. No setup needed for this part. On a Saturday afternoon I didn’t know where to type the commands from the …