Controller (Report Designer):

Treating the Report Designer as the Controller in Power BI makes sense because they are responsible for orchestrating how data (Model) interacts with the user interface (View). The designer’s decisions define how business rules are applied, how data is processed, and how the user interacts with it. In this sense, the Report Designer does act … Read more

Model-View-Controller

MVC, which stands for Model-View-Controller, is a design pattern used in software engineering, particularly in web and application development. It divides an application into three interconnected components, which separates internal data logic from the user interface, allowing for more manageable and scalable code. 1. Model:  2. View: 3. Controller:  Workflow Example: Benefits of MVC:

Marketing.Campaign_Details_Plus

The Marketing_Campaign_Details_Plus view provides an enriched and detailed representation of campaign metadata, serving as a foundational dataset for analysing and managing marketing campaigns. This view is designed to offer a structured, high-level summary of campaign attributes, ensuring clarity and consistency for reporting and decision-making. Key Features: Use Cases: The Marketing_Campaign_Details_Plus view offers a solid foundation … Read more

BusOpp.Dates

Purpose The Business Opportunity Dates view is designed to consolidate and standardise key date attributes related to business opportunities within the organisation. The Business Opportunity Dates view plays a critical role in tracking, analysing, and forecasting opportunity lifecycle events. By consolidating multiple date fields into a single structured dataset, it ensures better visibility, consistency, and … Read more

API Documentation: get.myhistory

Purpose The get.myhistory API and stored procedure facilitate interaction with the DataWarehouse, enabling users to retrieve historical views for analysis. Designed for PowerBI and Power Applications, it offers flexible parameters, customisable views, and outputs data in JSON format. By combining the adaptability of SQL stored procedures with a RESTful API, get.myhistory delivers a robust solution … Read more

Customer.Order

Purpose The Customer Order view provides a high-level “document header” for customer orders, designed to summarise and contextualise individual order lines within customer orderline views. It includes essential details such as order number, customer information, order dates, and status codes, serving as a consolidated source for tracking and reporting on customer orders. By connecting order-level … Read more

Customer.OrderStatus

Purpose The Customer Order Status view provides comprehensive insights into the operational state of customer orders. By tracking statuses, user actions, error messages, and lifecycle changes, it enables monitoring and reporting on the order lifecycle. This view is essential for identifying and addressing operational issues or errors that may impact order processing. Use Case Owner: … Read more

DataMarts.ArrayVersion

The introduction of the array version of data marts is designed to enhance flexibility and consistency, particularly in managing regional data that may vary in field type and structure. This approach involves grouping related data fields into JSON-like arrays or structures within SQL. Here’s an explanation of its benefits and mechanics: Key Points of the … Read more

Project.Value

Purpose The Project Value fact table is designed to display summarised financial data related to project hours, costs, and revenues. It integrates with dimension tables, such as project_details and client_details, to provide a comprehensive view of the financial performance of each project. The primary purpose is to support project management, strategic decision-making, and financial analysis … Read more