How priyankfeb/pbi-assoc_onboarding works
Project Type & Purpose
• Type: A BI dashboard/report built in Power BI.
• Purpose: Track onboarding steps for associations, with dynamic timelines, status indicators, and “days on‐time” calculations.
Main Components
A. Data Sources
• External systems (e.g., SQL databases, CSVs/Excel files, SharePoint lists)
B. ETL / Data Preparation (Power Query)
• Data connectors and transformation steps.
C. Data Model (Tabular)
• Loaded tables, relationships, star schema.
D. Calculation Engine (DAX)
• Measures: Timeline SVG, Days On-Time, status logic.
• As a separate layer or sub-component within the Data Model.
E. Custom Visuals
• SVG graphics (imported from Figma designs).
F. Report Definition (Power BI Desktop)
• .pbix file containing pages, visuals, filters.
G. Deployment & Consumption
• Power BI Service (cloud).
• End-users / stakeholders via browser or mobile app.
Architectural Patterns & Principles
• Layered architecture:
– Ingestion layer (connectors)
– Transformation layer (Power Query)
– Semantic layer (Data Model + DAX)
– Presentation layer (Custom SVG + Report pages)
– Deployment layer (Power BI Service)
• Single source of truth: centralized tabular model.
• Separation of concerns: ETL vs. modeling vs. visualization.
Technology & Tooling Details
• Power BI Desktop & Service
• M (Power Query)
• DAX expressions
• SVG assets (exported from Figma)
• Figma (UI mockups)
• GitHub (version control for SVGs, .pbix metadata)