UiPath Release Notes

UiPath Release Notes

Release Date: 1st September 2020

Bug Fixes

Correcting an inadvertent capitalization typo in a column name (e.g. successfullTransaction > SuccessfulTransaction) resulted in a persistent failed state for the data cube.
To resolve any duplicate file names following upgrade to v20.4.3, wait 30 minutes for all background processes to complete and follow these steps:

  1. Open C:\ProgramData\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\connector.log and search for duplicate column name errors (e.g. Validation error: Invalid table schema. Table Process-DuplicateColumn_tst-1 contains duplicate column names.).
  2. Open C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\uipath_insights.properties and set insights.case.sensitive=false.
  3. Restart the Sisense.JVMConnectorsContainer service.
  4. From the Insights SQL server, locate the uuid for the cube state file then query the datasets table for the process identified in step 1. For example:
select top 1 <uuid> from datasets where TableName  = 'Process-DuplicateColumn_tst-1' order by 1 desc
  1. Open the C:\ProgramData\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\state directory locate the file matching the uuid from above.
  2. Change the column name noting that the column name must already exist in the dataset, this process does not permit for new, at-will name changes.
  3. Login to your Insights instance and navigate to htts://<insights_url>:8081/app/data/:
    a. Select the table with the duplicate column name.
    b. From the More Options (. . . ) menu select Refresh Schema.
    c. Click on Build > By Table > Build.
  4. Repeat steps 4 - 7 for each table with duplicate column names.

Known Issues

If using SQL Server 2014 or earlier, all date time fields are displayed in UTC format.

Updated 18 days ago


2020.4.3


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.