I’m pleased to announce the Dataverse 3.2.2 release is now available.
This release provides the following enhancements to the Dataverse application:
- Additional capabilities for importing data from CSV and delimited files
- User interface performance improvements
- Execution performance improvements
- Conflict management for moved documents
This release also introduces a number of operational, performance and stability improvements.
Node Enhancements
CSV/Delimited Node
The CSV/Delimited Input node now offers additional flexibility in how the node can be configured. The property values for certain properties can optionally be derived from values contained in an input field. The ‘fromField’ option is now available for the following properties:
FileCharacterSet, Format, FieldDelimiter, EscapeCharacter, QuoteCharacter, IgnoreSurroundingSpaces, TypedHeaders, SkipHeaderRows
The node also provides three additional properties:
HasHeaderLine, DetectOnly, NumSampleRows
The file character set can be auto-detected by sampling the data rows. The maximum number of rows used in the detection process can be set using the NumSampleRows property.
The DetectOnly option configures the node to detect the format of the file but does not import the data. When the DetectOnly property is set to True, a third output pin must be added to the node to output the detected file format data.
Application Enhancements
User Interface Performance Improvement
The performance of the Dataverse UI has been significantly enhanced to improve responsiveness (up to 10x faster) when working with data flows that contain a large number of nodes in a single Composite node, in particular when:
- Navigating within the user interface
- Editing property values.
Execution Performance Improvement
Performance has been improved for concurrent execution of multiple data flows (by multiple users or schedules), loop execution and execution when running nodes that are processing small amounts of data
Move Document Conflict Management
When attempting to move a document between folders in the Dataverse directory view, a move conflict can occur if the destination folder contains a document with the same name or the same ID.
Dataverse now provides you with options to manage any move conflicts, enabling you to:
- Replace the existing document
- If the names conflict – rename the moved document
- If the IDs conflict – have Dataverse assign a new ID to the moved document.
Resolved Issues
The following issues have been resolved in this release:
- LAE-9058, LAE-9683, LAE-9810, LAE-9878, LAE-9914,
- LAE-10051, LAE-10057, LAE-10072, LAE-10080, LAE-10090,
- LAE-10131, LAE-10140 , LAE-10141, LAE-10144, LAE-10145,
- LAE-10146, LAE-10147, LAE-10150, LAE-10194, LAE-10195,
- LAE-10196, LAE-10301, LAE-10336, LAE-10356, LAE-10364,
- LAE-10372, LAE-10376
See the release notes for details of the resolved issues.
Comments
0 comments
Please sign in to leave a comment.