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
Order.item_dates_stage captures the order lifecycle timeline as a status-history “item” table. Each row represents a single lifecycle event (a status entry) for an order, with the event date carried as a meta-date value and the event details stored as JSON metadata. Use it when you need to answer questions like: Grain and keys This is … Read more
This release focuses on improving the reliability, regional consistency, and future-proofing of project and business opportunity metadata. Key improvements include a redesigned approach to project role handling, introducing dedicated role views and a new email-based identifier aligned with the emerging Person domain. Several legacy defects were corrected, including misclassified company identifiers, invalid JSON payloads affecting … Read more
✅ Green — Available and fit for purpose Use Green when: Outcome: Report builder can proceed with confidence. ⚠️ Yellow — Present, but not where/what we expected Use Yellow when: Outcome: Needs a small piece of investigation/remapping, but not a dead end. ❌ Red — Critical gap (blocking) Use Red when: Outcome: Requires Data Engineering … Read more