Steps to implement FTE Logic in Power BI
β What Youβll Need π οΈ Step-by-Step Power Query Approach Step 1: Load both tables into Power Query Step 2: Create a Cross Join (Employee Γ Month) Step 3: Add FTE Logic (Human Version in M) Now, for each row (i.e. employee Γ month), add a custom column to calculate the monthly FTE: π§Ύ Final Step: … Read more
Monthly FTE Logic
Each month, we assess whether and how much an employee is active in their role, based on their employment dates, status, and working pattern. The output is a monthly FTE value that represents their contribution in that month. Here’s how it’s determined: 1οΈβ£ If the person is seconded or transferred out We calculate how much … Read more
Release 66
This week, we have completed a significant set of updates, with 56 unique datamart view changes aimed at improving quality, modularity, and stabilisation across domains. Below is a summary of the key changes: π Bug Resolutions and Data Quality Enhancements Customer_ID Bug USD: Missing Fields Corrected in legacy views: Continuing our efforts to rationalise the … Read more
Fabric-Aligned Data Layering Model
Our data architecture follows a structured, layered approach based on the Medallion model. It aligns with Microsoft Fabric principles and best practices, supporting efficient data ingestion, transformation, governance, and reporting. Landing Layer This layer receives raw data files (typically CSV format) from external systems into secure landing zones. Bronze Layer Bronze provides the initial structured … Read more
Release 65
Scope: Updates to Common Data Model (CDM) and project-specific viewsTotal File Changes: 34 π Summary of Key Changes β Stabilised Views for 202409 Reporting These views are now stable and finalised for the 202409 reporting cycle, helping to prevent reuse issues in future CDM deployments. π οΈ Updated PRUs for Project Views CAD Region Updates: USD … Read more
Pipeline Execution Summary
Run Date: 21 April 2025Pipeline ID: run-all-cdm-viewsTriggered By: Scheduled AutomationAzure Environment: ProductionOverall Status: β SuccessViews Processed: 34 π View Execution Log View Name Status Row Count Duration (s) Notes project_core Success 11,203 12.4 employee_core Success 9,480 10.1 busopp_core Success 3,912 8.6 β¦ β¦ β¦ β¦ β¦ Data retrieved from ADF activity output and logged in … Read more
BusOpp.Codes
π Description This view provides a structured metadata representation of Business Opportunities (BusOpp), transforming source data into a JSON-like attribute-value format. It supports consistent reporting and simplifies analytics by organising attributes under clear META_TYPE categories like OPPORTUNITY, STATUS, and SALES. π― Purpose β Use Cases π§± Structure Each row in the view corresponds to a … Read more
Extended REST Semantics β In Simple Terms
Verb Meaning (Simple) Behaviour SQL/Data Analogy Use Case GET “Tell me about this.” Retrieves a resource or field SELECT * FROM table WHERE id = x Viewing a project status or employee detail POST “Hereβs a new thing.” Creates a new resource INSERT INTO table … New project added, first metadata entry PUT “Replace the … Read more
Release 64
Summary of Changes by View 1. project_details_plus_USD & project_details_plus_CAD Status Logic Updated Project Manager Email Added 2. project_details_plus_CAD & project_details_USD Column Name Adjustment 3. project_details_plus_APC, customer_details_APC, project_details_APC PRU Code Mapping Enhancement 4. global_company & global_company_202409 Expanded Source 5. global_organisation & global_organisation_202409 Same as Above 6. employee_item_codes_absence, employee_item_dates_absence, employee_item_values_absence Minor Logic Refinements 7. dates_DIM_DATE_202409 Performance Optimisation … Read more