What this view is for Project.meta_codes provides the categorical and classification attributes for projects. Where Project.core_details defines what a project is,Project.meta_codes defines how a project is described and grouped. If you’re asking “what type of project is this?”, “which programme does it belong to?”, or “how should this project be categorised?” — this is where … Read more
What this view is for Project.core_details is the starting point for all project-based reporting. Where: This view defines the project as a business object and provides the identity and links needed to relate delivery activity back to opportunities, orders, customers and ultimately invoicing. If you’re asking “what projects are we running, for whom, and how … Read more
Purpose evw.project_core_export_meta is a serverless-friendly export view that prepares Project objects for downstream document-style consumers (e.g. Cosmos DB, AI/ML pipelines, Graph preparation), without relying on unsupported Synapse On-Demand constructs such as stacked / correlated FOR JSON queries. It combines: This view is designed as a Stage-1 export: it yields tabular rows with embedded JSON strings … Read more
This template is designed to work as a reusable starting point for Sales Pipeline reporting across Busopp, Order and Invoice, using consistent datamart views and a parameter-driven connection pattern. The template can open and run “out of the box” if default values are provided (or if you enter the parameters when prompted). What you get … Read more
The Sales Pipeline is modelled as three connected domains, each representing a different stage in the commercial lifecycle. They are not duplicates of the same data.They are different truths at different moments in time. Understanding how they relate is the key to building accurate, trustworthy reporting. The three domains at a glance Think of the … Read more
What this view is for Invoice.item_values_lines provides the numeric values associated with invoices. Where: Invoice values represent what has actually been billed. This view is the authoritative source for invoiced amounts, tax and realised value. A note on “lines” in the CDM In the Common Data Model, lines indicates a value-bearing version, not necessarily a … Read more
What this view is for Invoice.meta_dates provides the key billing, lifecycle and payment-related dates for invoices. If: then meta_dates explains when important invoice events occurred or are expected to occur. This view is central to billing timelines, ageing analysis and cashflow reporting. Level of detail (grain) This view is intentionally long and thin.An invoice with … Read more
What this view is for Invoice.meta_codes provides the classification, status and commercial context for invoices. If: then meta_codes explains how the invoice should be interpreted, including its status, type, numbering context, payment terms and links back to upstream objects. This view is essential for understanding why an invoice looks the way it does and how … Read more
What this view is for Invoice.core_details is the starting point for all invoice-based reporting. Where: Invoices represent delivered and billed reality. This view defines the invoice as a business object and provides the identity and links needed to relate billing back to orders, opportunities, projects and customers. If you’re asking “what has been invoiced, to … Read more
What this view is for Order.item_values_lines provides the numeric values associated with customer orders. If: then item_values_lines answers how much has been ordered — in quantity, value and profit terms. This is the view where contracted order value lives. A note on “lines” in the CDM In the Common Data Model (CDM), the term lines … Read more