Purpose META_TYPE is used within CDM metadata views (such as meta_codes, meta_dates, and meta_values) to group related attributes into meaningful analytical categories. Rather than storing hundreds of unrelated attributes, META_TYPE provides a semantic grouping layer that helps analysts understand the nature of the data. Each row therefore follows a pattern similar to: OBJECT → META_TYPE … Read more
Purpose The Data Dictionary is the overarching governance process used to maintain the meaning, structure, lineage, quality rules, and operational control of data assets across the Data Platform. Rather than existing as a single document or table, the Data Dictionary is delivered through a set of linked artefacts, each addressing a distinct aspect of data … Read more
Provides project role assignment metadata in the standard CDM meta_codes structure, with regional view variants for APC, CAD, USD, UKS, and future IFS-aligned sourcing. Purpose The project.meta_codes_roles family provides a standardised project-role metadata pattern for identifying named project responsibilities against a project object. This allows project role assignments to be consumed consistently across regions even … Read more
Managing Dataflow Gen2 across multiple environments (Development and Production) can be a headache. By default, the destination Lakehouse or Warehouse IDs are hardcoded. This means when you deploy to a Production workspace, your dataflow might still try to write back to your Development environment. In this guide, I’ll show you a workaround to parameterize your … Read more
Release 92 absorbed in DEV Pipeline Release validation 1. BusOpp (EUR & NA) – Structural Refactor Views affected What has changed We have refactored the MP8 / MP9 source logic to remove duplicated transformation code and consolidate the sources via an early UNION pattern. The primary driver was identification of multiple editions of the same … Read more
Structural Consolidation, Export Alignment & ReportingUnit Introduction Overview Release 91 focuses on structural consistency across domains, export pattern alignment, identifier correction, and preparation for enhanced historical interrogation using get.myview. This is a maturity release.It strengthens foundations rather than introducing visible UI features. 1. Removal of Hard-Coded ACTIVE_FLAG Filtering Affected Domains Affected Views (cvw) Change Removed: … Read more
1. Never Use Underlining for Emphasis Rule:Underlining is reserved for hyperlinks. Full stop. Why? Underlining for emphasis is obsolete in professional digital documents. Exception: hyperlinks only. 2. Use Bold Intentionally — Not Emotionally Bold is not decoration. It is structural. Good uses of bold: Bad uses of bold: If everything is bold, nothing is. 3. … Read more
This release introduces structural improvements across Project Roles, Employee Codes, ReportingUnit, and Order Stage lifecycle tracking. 🔹 Project Roles – Structural Refactor Project Roles have been removed as a META_TYPE from Project.meta_codes. Instead: Why this matters This isolates regional and conditional role logic away from generic metadata structures, reducing complexity and making future changes safer … Read more
ReportingUnit.item_values_budget provides the budgeted order intake value at Reporting Unit (PRU) level, structured as an item-values dataset so it can be joined consistently with other CDM-style domains (actuals, forecasts, pipeline, etc.). It is sourced from sales.order_intake_budget, which is derived from the Finance-controlled budget workbook in SharePoint, and then reshaped into the standard OBJECT + ITEM … Read more