Release 47

by

Alterations Busopp.Details_Plus (beta) Complete the CTE (modular array) to include Dates and Measures/Values Busopp.Value Full version of CTE (modular array) Busopp.Dates Add New SEQ (Link sequence style) Customer.Orderline_202409 Include Project ID from QFACT_PRE_ACCOUNTING_OL$ as coalesce(cfv.CF$_PROJECT_ID,precfv.CODENO_D,src.DIM_PROJECT_ID) as PROJECT_ID, Notes Total number of different files: 2Total number of missing files in DEV CONTAINER: 0Total number of missing files in … Read more

Release 46

by

Additions Customer Invoice for Array Version (202411) Notes Numbered Comparison Results:1. 🔴 MISSING IN PRD CONTAINER: customer_invoicestatus_202411.sql2. 🔴 MISSING IN PRD CONTAINER: customer_invoicevalue_202411.sql3. 🔴 MISSING IN PRD CONTAINER: customer_invoice_202411.sql4. ⚠️ DIFFERENT: customer_orderstatus.sql Total number of different files: 1Total number of missing files in DEV CONTAINER: 0Total number of missing files in PRD CONTAINER: 3

BusOpp.Dates

by

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

by

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

by

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

Release 44

by

Additions: customer_order The customer_order view serves as a document header for the customer_orderline views, providing essential summarised information about customer orders. USD New Project views for North America (USD) myBMT Link for data perusalThese are planned to be delivered as APPEND/UNION to get.myview Alterations: Order Pipeline Further improvements to the ‘array version’ of Customer Pipeline … Read more

Customer.OrderStatus

by

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

by

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