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
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
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
Sharing local file links to Power BI (.pbix) reports may seem convenient, but it creates significant risks for your data, your reports, and your organisation. Here’s why this approach should be avoided in any enterprise environment. 1️⃣ It Creates Multiple, Conflicting Versions of the Same Report When a .pbix file is shared via local file … Read more
What this is MP8 and MP9 are regional “Opportunity & Order Intake” extracts used to provide sales pipeline and win/loss visibility where the opportunity lifecycle is not yet fully represented in IFS (or where we need historic continuity). This logic standardises the two extracts into a single, report-ready shape that aligns to our BusOpp-style reporting … Read more
What this view is for Project.meta_dates provides the date-based and lifecycle attributes for projects. Where Project.core_details defines what a project is,and Project.meta_codes defines how a project is classified,Project.meta_dates defines when things happen in the life of a project. If you’re asking “when did this project start?”, “when is it due to finish?”, or “when did … Read more