This release includes a number of features that were introduced in the 3.9.X releases, including execution sandboxing with Docker (server only) and new canvas alignment features.
ERP nodes to handle the max row count
The Extract ERP Table node will allow you to set the MaxRowCount that limits the number of rows retrieved when no RowCount is specified.
The RowCount property is used to limit the rows, however, if the SAP system does not allow for the default (2147483647) number of rows, the property can be "unhidden" then set on the node or set server-wide via adding a line in the cust.prop to:
- Fixed an issue where the Extract ERP Table node sometimes fails with an error "Option not valid".
- The Database Metadata node has been changed to make trigger queries against Oracle using DBA_TRIGGERS instead of ALL_TRIGGERS. This should remove the need for any trigger permissions via "grant create any trigger to <user>" and only select permissions should be required via "grant SELECT_CATALOG_ROLE to <user>".
- Ability to download node logs from the node right-click menu.
- Introduced the ability to disable the schedule for a data flow while it is running.
- Introduced fistExec, lastExec, and execCount functions to the advanced scripting capability of the Lookup node.
|Fixed an issue whereby it was not possible to rename the output pin on the Modify Field Prefix node.||LAE-28615|
|Fixed an issue in the Excel File node if a WorkbookSpec property was specified which did not have the start and end column defined, and the node was configured to DetectFieldTypes, and the header row in the Excel spreadsheet contained empty cells, the cells were not getting auto-named correctly and instead were winding up with field names from the first row of the data.||LAE-28351|
|The Database Profiler node will now report and internal errors that occur during the column analysis phase of the profiling to the node's error output but this will not cause the node to fail unless the FailureBehavior property is set tot Error.||LAE-28875|
|Fixed an issue whereby the Database Metadata node was reporting warnings about "USE statement is not supported" and causing the node to not retrieve correct information when running against an Azure Synapse database.||LAE-28939|
|Fixed an issue where attempting to list files in a sub-directory of the user's uploaded files (My Folder) directory, the file picker does not show the files in the directory when the file picker is re-opened following the selection of a file in a sub-directory.||LAE-28852|
|Fixed an issue where the ‘do output’ statement showcased different behaviour for LAE and Data360 Analyze||
|Fixed an issue on the HTTP node where the DataOutputFieldType property was not always being used if one of the other output field properties were set.||LAE-27559|
|Fixed an issue where logged errors are not displayed if a node completes successfully.||LAE-28619|
|Fixed an issue where system backups could occasionally result in the application winding up in a deadlock requiring an application restart.||LAE-27690|
Fixed an issue where the execute data flow does not finish until the backup is complete.
|Fixed an issue where system backups could occasionally result in the application winding up in a deadlock requiring an application restart.||LAE-27566|
|Fixed an issue whereby Data360 Analyze services does not start when installing with restore from backup.||LAE-28774|
|Fixed an issue when running the Database Metadata node against an Azure Synapse database, if there were more than 32 thousand columns across all tables in any single schema, the node would log a warning and not retrieve any of the columns for that schema.||LAE-28941|
|Fixed an issue in the Database Metadata node, the table columns, and procedure and function parameters outputs previously had a null catalog field when run against postgres.||LAE-28966|
|Fixed an issue in URL Query Builder Node whereby fields specified Excluded Fields property were not excluded.||LAE-28948|
|Fixed an issue where toggle temporary transparency was not working for Textbox.||LAE-28784|
|Fixed breancrumbs on upload file to server dialog.||LAE-28927|
|Fixed an issue whereby the d3sa.api.rest.host or ls.brain.webapp.contextUrl where not used when creating the URL for the URL_To_Linked_Run property in the failed schedule e-mail notification.||LAE-28819|
|Fixed an issue where in the Database Metadata node for DB2, the Procedure Parameters output had a field called TABLE_NAME which should have been called PROCEDURE_NAME. On the Function Parameters output, it had a field called TABLE_NAME which should have been called FUNCTION_NAME.||LAE-28804|