DTL-SV130-XPFv4.3.0-PV930 Release Notes

Author: Matthew Lindon, Created: 2026-06-23

Release Date

August 3rd, 2026

Redesigned the AI Data Tools Security page for a more responsive UI and improved information display.
Reorganized the Query Composer UI to more closely mirror established precedents.
Reorganized the File Explorer UI to reduce button clicks and surface content quicker.
Added the ability to set a string column’s maximum length when configuring via the ETL dialog. This value defaults to 4000 but can be changed to one of 5 preset values.

Added a hover tooltip for the Last Selected Table, allowing users to read the full table or file name should it be too longer to display in full.
Added automatic delimiter detection for .csv file uploads via the ETL dialog.
Added defined schema assignment to ETL Database destinations.
Added distinct Schema and Table columns on the Query Composer page to support filtering.
Added Quick Action support for querying .psv and .tsv files.
Removed access to the Natural Language to Query function under conditions where the user either should not or cannot utilize it.
Vastly improved parquet read support for the ETL process, reducing time and increasing compatibility with multiple formats.
File size is now displayed using the most appropriate unit as opposed to always in bytes.

Fixed a bug where incredibly large .parquet files would refuse to load in File Explorer. This has been mediated by displaying a 1,000 row preview, as table querying should be performed within the Query Composer instead.
Fixed a bug where altering a table via the Edit dialog would require a table rename.
Fixed a bug where the table names grid would refresh in an unwanted scenario.
Fixed a bug where unsupported display types for File Explorer files would be displayed to the user.
Fixed a bug where the optional Date column during the ETL process would not be preserved when navigating back to the Date Range step.
Fixed a bug where Natural Language to Query context would not be accurate to the selection state.

Due to how individual queries are executed, commands that are intended to maintain state on a connection such as TRANSACTION, SET, CURSOR and others will not persist across queries. Every query operates on a new connection.