Dataverse enhancements in this release include:
Data Viewer Data Quality Indicators
Data Viewer data quality indicators provide an immediate view of potential data quality issues in each field. A histogram and sample statistics provide additional information on the (sample) data displayed in the data viewer.
Data Viewer Additional Filter Operators
The Data Viewer’s filter operators not support ‘Is Null’ and ‘Is Not Null’ making it easier for data analysts to identify and handle missing data. The filter criteria can be used to add Filter and Split Nodes to the canvas – without using any coding.
Excel File Type Detection
The Excel File node now detects the data type of the imported fields – streamlining the acquisition of data from spreadsheets.
Python Transform Node
The (Experimental) Python Transform node allows Data Engineers and Data Scientists to build custom data transforms using the Python language. This allows users to re-utilize existing coding skills without having to learn a proprietary scripting language. It also enables users to leverage publicly available help/forum resources and documentation to identify solutions.
JDBC Query and JDBC Execute Performance
The performance of the JDBC Query node and JDBC Execute node has been significantly improved when querying data in Oracle, especially for larger results sets.
Convert to Library Node
You can now convert selected nodes on the canvas into a library node. This enables you to re-use proven analytic logic in other projects and share components with colleagues - enhancing trust in the data, improving productivity and helping you to produce repeatable and auditable results.
Run Now Option for a Scheduled Data Flow
You can now choose to manually run a selected schedule, enabling you to test a schedule and specify any required Run properties.
Single Sign-On (SSO) Integration Support
When deploying an instance of Dataverse Enterprise Server edition the instance can now be configured to integrate with CA Technologies’ Single Sign On Siteminder Access Gateway/ Siteminder Secure Proxy Server to allow users to be authenticated using SSO.
Dynamic User Creation
Where a Dataverse Enterprise Server deployment has been configured to use SSO or LDAP/AD integration, Dataverse can also be configured to automatically create a user within Dataverse the first time they log in if the user does not already exist.
Automatic LDAP/AD Synchronization
When Dataverse Enterprise Server is configured with LDAP/AD integration, Dataverse can be configured to automatically synchronize with the LDAP/AD server at regular intervals.
User Role Enhancements
A new ‘Explorer’ role has been added to allow data flow ‘consumers’ to collaborate with designers and manage scheduling tasks. The ‘End User’ role has been renamed to ‘Designer’ and the ‘Scheduler’ role has been renamed to ‘Designer – Scheduler’.
Audit Logging Documentation Enhancements
The Dataverse audit logging documentation has been expanded in this release to explain how the audit entries map to user actions.
Resolved issues include:
Processing date data types
When processing input fields that contained a date data type, the Change Metadata node and the Data Converter node would incorrectly output the year element for years after 1970. This issue has now been resolved. LAE-8778, LAE-8734
Decision Forest node
Resolved issue with the Decision Forest node where unstable results were generated due to an incorrect default parameter value being sent to the embedded R node. This issue has now been resolved. LAE-8189
Importing legacy data flows
Previously, Dataverse would fail to import a legacy data flow if the legacy data flow contained a Composite node with multiple Bypass nodes or Bundler nodes, or if the legacy data flow contained an instance of a library node that had an equals sign (=) in its name. These issues have now been resolved. LAE-8826, LAE-8823
Running legacy data flows
Previously, legacy data flows containing run properties that were set as "required" would fail to execute. This issue has now been resolved. LAE-8893
CSV/Delimited Input node
The default delimiter is now correctly dictated by the value set in the Format property if no value is specified in the ‘FieldDelimiter’ property. LAE-8743
Resolved issue with the CSV/Delimited Input node so that it now works correctly when the ‘|’ character is used as the ‘FieldDelimiter’ and a comma-separated list of fields is specified in the ‘FieldNames’ property. LAE-8852
Data viewer display of white space
The data viewer now correctly displays leading and trailing white space for field values. LAE-8854