Today, we’ve published a minor release of TimeXtender Data Integration (v. 6963.1) that contains the changes listed below.
Improved
- Improved the Ingest logic that manages data source providers to no longer try to download deprecated providers which caused confusing error messages.
- Renamed display names to no longer include "Semantic"
- Removed the limitation of reserved words for custom field validations and custom conditions
Fixed
- Fixed a wrong icon for super natural key fields in data lineage and Perpare table selection.
- Fixed various typos in the TDI application.
- Fixed an issue where the Metadata Manager in Ingest would produce a change notification for columns without the ‘original data type’ metadata.
- Fixed an issue with deploying Hierarchy tables with ‘Null check approach’ set to ‘Record Based’
- Fixed an issue in Ingest on Fabric Lakehouse storage where tables were not transferred correctly if they contained ancient dates.
- Fixed an issue where the ‘StepODXDataFactoryExecute’ was not cleaned up when the last table was removed from an execution package that allowed that step to exist.
- Fixed an issue where Convert to Mapping Set was incorrect for fields with custom transformations.
- Fixed an issue where Integrate Existing Objects was affecting existing views.
- 23785: Primary key check is getting skipped when a table has no mappingsThis issue was corrected - It affected tables with no mappings but having custom data, table inserts, and/or related records.
