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
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.item_values provides the numeric and financial measures for projects. Where: If you’re asking:“how much has this project cost?”,“how much revenue has it generated?”, or“what is the current forecast or contingency?” — this is where you look. Architectural maturity This view is delivered as a cvw (collated view). It is assembled … Read more
The MP8 and MP9 import process is used to bring regional opportunity and order-intake information from Finance spreadsheets into the Data Warehouse in a consistent and repeatable way. What this process is for This process ensures that: It is primarily used where opportunities exist in regional or pre-IFS systems and are not yet fully represented … Read more