Summary of Data Required for Business Opportunities

Across our Business Opportunity data marts, we request information in five broad categories. These allow us to report pipeline health, opportunity quality, value, customer context, and alignment with programmes and sales structures. 1. Core Identifiers These are essential keys that allow us to uniquely link and track opportunities across systems. These form the backbone for … Read more

Release 83

Release Date: 18 November 2025 Overview This release introduces a number of improvements across customer, supplier, order, employee, and project data. Most updates focus on strengthening data quality, improving historical accuracy, and preparing for future Common Data Model (CDM) enhancements. No breaking changes are expected for reports. Key Improvements 1. Better Employee and Person Data … Read more

Release 82

Release Notes – Week Ending 10 November 1. Feedback Meta Views Files: Summary:The former feedback_meta_codes_satisfaction view (over 800 lines) has been decomposed into its logical components to improve maintainability and clarity. These sub-views—covering Customer Voice, Customer Thermometer, Legacy External, and Legacy Internal—are now individually managed and combined through the new feedback_meta_satisfaction UNION view. This marks … Read more

Gen2 Dataflow Pattern

SharePoint list → cleaned, flat, ISO-dated table A reusable Power Query (M) snippet for Dataflows Gen2 that: When to use: Landing SharePoint list data into a Bronze/Silver layer (Fabric/Synapse/SQL) where flat, predictable schemas, text-formatted dates, and stable column names are preferred. Full code (drop-in) Step-by-step Customisation points Validation checklist Troubleshooting Notes

Release 81

Weekly Release Note – Week Ending 03 November 2025 New Views project_meta_codes_pmn A new DataMart view based on data sourced from the SharePoint List PMN, processed via a GEN2 Dataflow to the Bronze layer.🔗 View Documentation This view enables portfolio and project management insights by transforming Project Manager Narratives (PMNs) into a structured, analysable format. … Read more

🧩 Function: UrlEncode

Category: Utility Functions → String & EncodingAuthor: Data EngineeringLanguage: Power Query (M)Purpose: Converts a text string into a URL-safe format by encoding non-alphanumeric characters as percent-encoded hexadecimal values (%XX).Compatibility: Power BI, Excel Power Query, and Fabric Dataflows (Gen2) 📝 Description UrlEncode transforms text into a format suitable for inclusion in URLs or API query strings.All … Read more

GeneralLedger.Item_Codes_Balance

Purpose This view supports financial control and transparency by standardising balance-level data for consistent reporting and reconciliation. It helps finance and business leaders understand balance movements, inter-company positions, and the relationship between projects, programmes, and cost centres. Use Case Suggested dashboard insights: Source Integration with Dimension / Reference Tables Joins used (per SQL): (none in … Read more

GeneralLedger.Item_Codes_Transaction

Purpose This view provides a clear and consistent way to analyse individual General Ledger transactions across the organisation. It breaks each posting down into structured attributes — such as journal, project, programme, or inter-company activity — so that financial movements can be explored, reconciled, and connected to operational detail. Use Case Suggested dashboard insights: Source … Read more

GeneralLedger.Meta_Codes_Details

Purpose This view provides a consistent and detailed picture of General Ledger activity across the organisation. By standardising ledger attributes and dimensional codes, it enables reliable analysis of financial movements, balances, and reconciliations — all within a single, governed structure. This view supports finance and audit teams in maintaining clarity and confidence in financial data. … Read more

Release 80

DataMart views changed since 01-Oct-2025. Executive summary New views Renamed / globalised Downstream dependencies: Corrections Improvements to source identification & aliasing Purpose: Ensure tables are identified using their non-dollar names for lineage and metadata consistency. Change pattern:'{“Source”:”ifs.[QFACT_BMT_DWH_INVOICE_TAB_IAS$]”}’ as SOURCE_SYSTEM→'{“Source”:”ifs.[QFACT_BMT_DWH_INVOICE_TAB_IAS]”}’ as SOURCE_SYSTEM Views updated: Global query structure change (Beta & 202409 queries) Adopted a consistent CTE … Read more