The table [acco].[Lineage] holds the lineage metadata, which is used to find and run stored procedures throughout the OneDB, related to a given dimension or fact table.

The stored procedure [accoRUN].[sp_Process_Changes] is a helper procedure for running UpdateModel = 0, to repopulate changed or new objects, and their dependencies. This avoids having to full load the entire data warehouse, when isolated changes are needed.

Multitenant / Multienvironment support

The finance hierarchies are designed to organize and structure financial accounts in a way that supports both detailed analysis and high-level reporting. This functionality is primarily built on two components:

This dimension contains all financial accounts imported from the ERP system, including both posting accounts (used in actual transactions) and total accounts (used for aggregation). While only posting accounts are directly linked to financial transactions, total accounts serve as structural elements in the hierarchy.

This component defines how financial accounts are grouped and displayed in reports. It includes the hierarchical structure of accounts, allowing users to view financial data at various levels of granularity (e.g., account -> group -> category). It also supports custom mappings and ERP-specific structures, enabling flexible reporting across different systems.

Together, these components enable:

The global dimensions framework enables flexible and scalable filtering, grouping, and analysis of data across multiple business perspectives. It is structured around two key components:

This table acts as a central grouping mechanism for all global dimensions. It follows a snowflake schema, where all fact tables (e.g., sales, finance, inventory) relate to Dim_DimensionSet, which in turn connects to the individual global dimension tables. This design ensures consistency and reusability across the data model.

*

These are the individual global dimension tables, such as:

Each table contains a key, a name, and optionally a hierarchy that defines parent-child relationships within the dimension. These dimensions provide the semantic context needed for slicing and dicing data in reports and dashboards.

Budget module has been redefined using the latest accoPlanning features, reducing complexity within the data warehouse.

Admin Center updated to integrate with accoMasterData for streamlined management.

Introduced a modernized report design for the following modules: Finance, Sales, Purchase and Inventory, and Budget.

The new layout offers a cleaner look and more space for individual visualizations, enhancing readability and user experience.

Extended the API for BC Cloud with our own extension to BC, enabling better integration and access to more columns, without relying on OData.

The entire data flow, from the Datawarehouse to the Semantic Model and Reports, has been refined to improve performance and eliminate redundancies.

A new naming approach has also been implemented, which includes clear data source and module specifications. This ensures that only the relevant data source(s) and module(s) required by the customer are applied to their data model, improving overall efficiency.

Additionally, a few tables have been renamed to enhance clarity and consistency across the model.

The product has been upgraded to the latest data warehouse framework accoONE-DB 2.2. This new upgrade introduces a more streamlined data structure, significantly reducing complexity. By optimizing data source and module control, the update ensures that redundant tables are automatically excluded, resulting in enhanced system performance.

With this new tool, the process of creating a semantic model on top of the Datawarehouse is now automated. The framework efficiently builds tailored data models, saving time and simplifying the setup process.

The currency conversion process has been simplified, reducing the complexity of measures within the data model. This simplification makes it easier for users to work with and understand the measures.

To improve data consistency and ensure seamless deployments, unique key constraints have been implemented for Meta Data tables. This enhancement helps maintain data integrity during transitions from development to production environments.

The guide for setting up and configuring Business Central Cloud now includes instructions for integrating Microsoft Entra Applications, ensuring smoother implementation.

Performance improvements have been made to Finance Drill pages, offering faster data retrieval and better user experience during financial data analysis.

Leveraging Microsoft's PBIR to enable smart version control for Power BI Reports.

Reduced Azure costs through enhanced optimization for both Business Central On-Premise and Navision integrations.

The data model has been expanded to include Purchase Credit Memos, enabling better tracking and reporting of purchase returns and adjustments.

The accoONE-DB has been rewritten to be based on a common data model, where the data lineage flow for the accoONE-DB is located. This means that you can track what happens to e.g. a extModel view throughout the data warehouse flow.

This enables more advanced automations, as it simplifies the way automatic objects are created. Furthermore it enables isolated data warehouse runs for e.g. a fact or dimension with their dependencies, without running the entire data warehouse flow.

The following features has been developed on top of this:

To keep a clean structure a dedicated schema for consolidated data sources and persisted stgModel views has been created named - stgConsistency.

This new upgrade introduces a more streamlined data structure, significantly reducing complexity. By optimizing data source and module control, the update ensures that redundant tables are automatically excluded, resulting in enhanced system performance, especially for BIaaS products.

PBIDataModelManipulator configuration table has been added to enable use of Accobats Power BI framework.

Introduced a template for creating native Power BI solutions focused on project and employee performance, leveraging the job section in Business Central.

Introduced a template for creating native Power BI budget solutions, facilitating budgeting for P&L and Sales.

Enabling version control and employee access management.