TEAM v.1.6.8

New features

• Improved the way the physical model snapshot is maintained as a JSON structure. For very large solutions it can become cumbersome to manage this in a single file. TEAM v1.6.8 changed this so that each table or file is saved in JSON as its own file. These files are organised in a <connection/database> / <schema/container> / file directory structure. Having separate files for each data object makes merging changes via Git much easier
• Added an import feature for (now legacy) tabular physical model JSON files. Loading a file now creates the contents as separate files in the aforementioned structure
• Modified the filter criterion to be case-insensitive everywhere (this only applied to the mapping grids in the previous version)
• Pressing 'end' in the data item mapping grid will now enter the cell (edit mode) and navigate to the end of the value in that cell. This is an improvement when editing the grid in many places
• Added full-row duplicate check for the data item mappings. If a duplicate is present in the grid, the validation process will report this (if duplicate detection is enabled in the validator form)

Breaking changes

• TEAM v1.6.8 will expect a 'PhysicalModel' directory in the designated metadata directory, and create this if it does not exist. The physical model grid will use this directory to manage the physical model snapshot. Previous versions, that use the 'TEAM_Model_Metadata.json' single file will initially not see the physical model, because TEAM expects the separate data object JSON files to be present in the PhysicalModel directory. To convert, please import the TEAM_Model_Metadata.json file using the Physical Model Import feature, available in the menu. This only needs to be done once, after which the TEAM_Model_Metadata.json is no longer required.

Bug fixes

• Updated the hash key approach for data item mappings to be truly unique for each row in the data item mapping grid. Previously, a hash value was issued upon creation. In some cases, when many records are created the same way in a bulk process and later completed, this would result in multiple mappings having the same hash key. An update in one would then be applied everywhere. This fix will prevent this from ever happening again
• Fixed issue where the grid view would sometimes not render if an incorrectly structures JSON file was in one of the metadata sub-directories
• Handled exception where the 'previous data object name' was not found during bulk-parsing