🔧 Summary of Changes This week’s release includes updates to four DataMart view SQL files, all related to a recent data unification issue affecting the CAD domain. The issue arose due to conflicting records across two client lists. This has now been resolved by aligning with the authoritative CL extracted from the Vision database (last … Read more
📘 Context The CODESSTRING field returned from Oracle contains serialised key-value pairs using non-printing ASCII characters: Example value: ✅ Goal Convert this encoded string into structured columns in Power BI, e.g.: ACCOUNT CODE_B CODE_C CODE_D CODE_E 10201 200 2011072 🛠️ Solution: Power Query Function Step 1: Create the Parsing Function Step 2: Apply the Function … Read more
Direct Sources Indirect Sources
🗂️ Summary by Change Type Many of the changes in this release were introduced to support the dynamic generation of Common Table Expressions (CTEs) as part of the myBMT auto-creation logic. As such, the majority were structural or naming updates to improve integration and metadata alignment. There were limited functional changes, namely: Change Type Example … Read more
✅ 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
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
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
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
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