How to Raise a Change

Continuous improvement depends on clear, well-defined change requests. Whether the request is a small enhancement, a logic correction, or a larger structural improvement, good change information allows the right people to assess, prioritise, and deliver efficiently. Poorly defined requests create delay, rework, and misunderstanding. Well-raised changes move faster. This guide explains how to raise a … Read more

Change Levels Matrix: Choosing the Right Route for Change

Changes to data, reporting, and analytics services vary significantly in complexity and risk. Some are simple service improvements. Others may affect trusted figures, operational decisions, or access to sensitive information. To support timely delivery while maintaining confidence, changes should follow a route proportionate to their impact. This matrix helps classify requests consistently and select the … Read more

Safe Data Explained: How We Change Reporting Responsibly

Modern reporting environments need to improve continuously. New requirements emerge, defects are identified, source systems evolve, and opportunities to simplify or optimise are found every week. Not every change carries the same level of risk. Changing a label on a report is not the same as changing revenue logic. Improving performance is not the same … Read more

Release 96

A strong week of structural improvement, model refinement, and practical fixes across the Common Data Model. The focus has been on better relationship modelling, clearer taxonomy, stronger export readiness, and higher-quality project transaction data. πŸš€ Major Enhancement: New Bridge Table Type Introduced The new Bridge table type has now been extended into production-ready use cases, … Read more

Release 95

This release materially strengthens the platform by: 1. Catalogue & Metadata-Driven Pipeline Foundations 2. Enterprise Domain Expansion 3. Sustainability & Compliance Enhancements 4. Employee Domain Standardisation (UKS Alignment) Renamed and aligned all Employee views to UKS versioning: Key Changes 5. Resource Domain – Activity Model Refactor New views introduced: Change Summary 6. Identity Domain – … Read more

Release 94

Summary of Impact πŸ”§ Project Domain Enhancements Project Meta Codes – Roles Project Meta Codes (Core View) Project Manager Attribute – Reinstated Project Item Codes (UKS) πŸ‘€ Person Domain (New) Core Views Person Meta Codes 🧾 Invoice Domain Update Invoice Meta Codes πŸ“Š Business Opportunities (APC) busopp_details_plus_APC πŸ’° Finance Domain Expansion Accounts Receivable – Item … Read more

Release 93

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

Release 91

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

Release 90

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

Release 89

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