I am pleased to announce the Dataverse 3.1.2 release is now available.
This GA release provides Data Analysts with additional script-less node configuration functionality and extends our data-driven authoring capabilities which enable the creation of nodes from within the Data Viewer.
The release enhances our Excel publishing integration capabilities and also sees the introduction of new java-based nodes that are drop-in replacements for some of the existing C++ based nodes. We have also resolved a number of issues that affected the BRD, Cat, Excel, JDBC and QVD nodes.
Users in Turkey will also be pleased to hear that we have resolved the issues that were preventing users from successfully installing the Dataverse product. Similarly, the handling of non-US ASCII characters has been improved – which resolved issues encountered by users in non-English speaking countries and users working with non-English character sets.
In addition, the release delivers numerous performance, stability and usability improvements.
Script-free Configuration of Split Node
The Split node now provides an easy-to-use editor that enables the Split node to be configured without using Dataverse script.
- The Field name can be entered manually or picked from the input field list. In addition to the name, the data type of the fields are displayed:
- The comparison operator and value are configured in the grid. The listed operators depend on the data type of the selected field.
- Multiple criteria can be included in a filter group. You can match:
- all criteria in the group
- any of the criteria
- none of the criteria (i.e. logical NOT).
Multiple criteria groups can be created. You can choose to satisfy the criteria in all groups or any group.
- You can view and, if required, edit the Script generated by the node.
Data-driven Configuration of Split Node
You can leverage the data-driven authoring capabilities of the Data Viewer to also create a Split node without using any scripting.
- The first step is to open data set in the Data Viewer and apply the required filters.
- The Data Viewer's 'Split (on filters)' menu option is then used to add the configured Split node to the canvas.
- The R node is now available for use with Dataverse 3.1.2.
- The R node provides an interface to the R computation platform, allowing R scripts to be executed using Dataverse data sets, producing tabular or graphical output which is returned to Dataverse.
- The R node archive can be downloaded from the downloads page of the Lavastorm website:
- The R node uses a TCP/IP connection to communicate with an R environment. This connection is provided by ‘Rserve’.
- For Dataverse to communicate with the R environment, the Rserve server must be running on the machine hosting the R environment.
- The machine hosting the R environment must have sufficient available RAM to process the data
Note: R and the RServe client are not distributed by Lavastorm.
Open-source R is available under separate open source software license terms and is not part of Dataverse. As such, Open-Source R is not within the scope of your license for Dataverse. Open-source R is not supported, maintained, or warranted in any way by Lavastorm. Download and use of Open-Source R is solely at your own discretion and subject to the free open source license terms applicable to Open-Source R.
BRD File Node Enhancement
- A single BRD File node can now read Multiple BRD files by passing the file paths into the node on an input pin.
Output Excel Node Enhancement
- Multiple data sets can now be output to the same worksheet.
- The 'OutputSpec' property is configured to position the input data sets in the worksheet:
Output Excel / Append Excel Node Enhancements
- The Output Excel node and Append Excel nodes now support XLSM files.
- The Java heap space available to the nodes has also been increased to 2GB to improve the operation of the nodes when using certain memory-intensive optional properties e.g. when ‘Preserve All’ is selected on the ‘ExistingDataPreservation’ property on the Append Excel node.
Other Dataverse Application Enhancements
Data Viewer Enhancement
- The performance of the Data Viewer has been significantly improved when filtering large data sets.
Designer Canvas View Enhancement
- The responsiveness of the canvas has been improved, for example when opening a data flow or drilling into composites.
Dataverse Server Features
- The Dataverse Server editions now support an additional user role.
- The ‘Scheduler’ role provides the functionality of the ‘End User’ role plus the ability to schedule data flows and maintain schedules.
- Unsupported type specification warnings - The Cat, BRD File and Output BRD could generate an ‘unsupported type specification’ warnings when processing certain data types. This has now been resolved. LAE-8161
- Cat Node execution terminated error - Resolved the issue that caused the Cat node to generate an ‘execution terminated’ error. LAE-7629
- Excel File incorrect dates - Resolved the issue when reading dates from formulas, the century of the date could be incorrect. LAE-8509
- Excel File zip bomb handling - Previously the Excel file node could report a valid file as containing a ‘zip bomb’. The node now provides the ‘TrustedSource’ property that enables you to specify the file is from a trusted source, allowing the node to run successfully when previously it would have generated a zip bomb error. LAE-8454
- Output Excel Node handling of invalid pin names - Previously, the Output Excel node would error if the name of a pin was invalid. The node now modifies the name to remove invalid characters and generates a warning message. LAE-7540
- Output Excel Node generated file size - When the data contained empty cells, the generated file could have a large file size. This has now been resolved. LAE-7438
- Output Excel Node creation of output pins - As the express purpose of the Output Excel node is to output data to a file, the ability to create additional output pins has been removed. LAE-7486
- JDBC Nodes handling of Nulls with Postgres driver - The JDBC Store and JDBC Execute nodes can now load NULLS for all data types using the Postgres JDBC driver. LAE-8528
- JDBC Nodes handling of Unicode data types - An issue was identified that prevented the JDBC Store node from accepting Unicode input data. This has now been resolved. LAE-8526
However, there is an ambiguity in the JDBC specification relating to how to bind to string data, since multiple methods exist on the ‘PreparedStatement’ object. To allow for this ambiguity, a new property called ‘UnicodeBinding’ has been added to the JDBC Query, JDBC Execute and JDBC Store nodes, allowing you to specify how the JDBC node binds Unicode values
The default value is recommended for all JDBC drivers unless you experience an error related to loading Unicode data types
JDBC Query on Snowflake cloud database - The JDBC Query node can now be used successfully with a Snowflake cloud database. LAE-7846
- JDBC Nodes handling of time fields - Previously, when storing data from a Dataverse ‘time’ field into a database using JDBC Store and JDBC Execute nodes, the ‘DefaultDate’ property added a date to the fields, regardless of the target database type. This issue has been resolved to prevent a date being added when storing time fields into string types in a database. LAE-8614
- JDBC Query default data type for strings - The JDBC Query ‘DefaultToUnicode’ property now defaults to ‘True’ meaning that string fields default to Unicode type. LAE-8619
- QVD File Node output zeros - The QVD File node could incorrectly output ‘0’ values when reading some QVD files. This issue is now resolved. LAE-7225