Today, we’ve published a minor release of TimeXtender Data Integration (v. 7303.1) that includes a fix for an issue with incremental load and mapping sets as well as a handful of fixes for Fabric Lakehouse as instance storage.
We recommend that you install this hotfix if you're affected by the issues we’ve fixed.
Fixed
- After upgrading to 7257.1, tables with incremental load configured in Ingest that was brough into Prepare though a mapping set were ignoring their incremental rules and running full loads on every execution.
- In Ingest instances on Lakehouse storage, if running with a user account that lacked access to certain objects, the entire table listing operation would fail.
- In Ingest instances on Lakehouse storage, no table is created when the table in the data source is empty. This would cause a “path not found” error when copying data to Prepare since the logic expected a table to be present even if there was no data.
- In Prepare instances on Lakehouse storage with multiple data areas, tables were generated with DW_Id = NULL and DW_Batch was not using the right value. Both values are now populated correctly.
- In Prepare instances on Lakehouse storage, the value of the Source Table column was incorrect for unmapped tables.
- In Prepare instances on Lakehouse storage, selection rules were not being respected during execution on aggregate tables and table inserts.
- In Prepare instances on Lakehouse storage, conditional lookup fields with spaces in their names would cause errors during execution.
- In Prepare instances on Lakehouse storage, an error would occur when creating supernatural keys in certain configurations.
- In Prepare instances on Lakehouse storage, failed executions in the execution queue were displayed as successful.
- In Prepare instances on Lakehouse storage, failed tasks were not listed in red in the Execution window, making failures harder to spot.
