TEAM v.1.6.10

New features

• Better handling of schemas. The data grid will always interpret schemas, but only show the schema where it differs from the default schema that is defined for the corresponding connection. Only if the schema is different, it will be visible in the data grid. In all cases will the schema be saved as an extension.
• You can now modify data object mapping classifications from TEAM, so that it can automatically be linked to certain templates in VDW.
• Extended query timeout to 10 minutes, in some (rare) cases, the reverse-engineering would time out because the retrieval of the physical model snapshot took too long.
• Created a support directory upon install with some useful scripts.

Breaking changes

• Not really a breaking change, but if the export feature to add the 'schema' to the connection extension is enabled, this will also be added at data object level. This is for done for (future) backward-compatibility. Conceptually, this is a property of the data object, not the connection.

Bug fixes

• Fixed a bug that prevented adding data items to the JSON file when the physical model is not yet available (to get the data type). Now, it will be added without a data type, because this is not known yet.
• Typo in Target Data Item column header for the data item grid.
• Fixed a bug that overwrote mapping-level classification changes.
• Fixed a bug that overwrote mapping-level extensions.
• Fixed a bug where data objects with the same name, but different connections were considered the same.
• Fixed a bug where the connection was not loaded correctly (because of JSON syntax errors made by users/outside of TEAM) but didn't notify the user.