Skip to content

TEAM v1.6.5
Compare
Choose a tag to compare
@RoelantVos RoelantVos released this 02 Nov 23:53
· 244 commits to main since this release
v1.6.5
48922c5

Overview

TEAM 1.6.5 is a major revision. The key change is the removal of the (central) metadata repository, which meant having a dependency on SQL Server. In this new TEAM version, no database repository is required anymore.

Not requiring a central repository removes various issues around multiple project teams contributing to the design, potentially impacting and/or overwriting each other’s work.

Instead, TEAM now directly interacts (reads and writes) to the data warehouse automation compliant JSON files that it would produce in earlier versions. The collection of JSON files effectively is the repository, and downstream code generation access the same files.

This means that the existing ‘activate’ process has been removed, because there is no longer a need to convert design into JSON files. Similarly, the ‘version’ concept is removed. This is because the JSON files would be located in a Git repository which handles versioning of the design metadata, along with the snapshot of the physical models and data logistics (code generation) patterns.

The combination of the JSON files (design metadata), the physical model snapshot and the code generation patterns allow for ‘time travelling’ for the solution itself, enabling deterministic reproduction of the model version at a point in time.

Other changes include:

  • Introduction of a ‘metadata’ path that captures where the JSON files are located
  • Stronger separation of environments, allowing configuration of paths per environment
  • Updated sample data
  • Support for Multi-Factor Authentication to access Azure databases for reverse engineering of the physical model
  • Ability to preview the JSON model in the app
  • Ability to override JSON segments in the app, for example to add custom extensions
  • Support for the ‘data query’ concept at both object and item level, e.g. the ability to define logic as a source instead of a table or column. Using `` will generate a dataQuery segment
  • Updated metadata importer to load legacy tabular JSON table mappings and generate these directly as data warehouse automation schema JSON files
  • Added physical model query generator to assist automating snapshot creation for the physical model
  • The distinction between ‘virtual mode’ and ‘physical mode’ has been removed. The only mode is what used to be ‘virtual mode’, which means all validations run against the snapshot of the physical model, and this tab is always visible
  • Multi-Active Satellites are now generated as extension for the target data item, so that these can be used in code generation patterns
  • Addition of a ‘purge’ feature to (re)apply generic settings to all mappings / JSON files

Breaking changes

Since the paths are now stored against the environment, the app will report an error the first time it is opened with older configurations. The resolution is to either remove the files in the ‘core’ directory (they will be recreated) or update the paths in the app and save

The way the JSON files are created for dimension- and fact target data objects has changed. Previously, each mapping would contain multiple source data objects. Now, each data object is in a separate mapping. This means presentation layer patterns need to be updated. Changes as part of VDW 1.6.7 will address this.

Assets 3
Loading