Saturday, August 22, 2020 - 18:56
Released COZYROC SSIS+ 1.9 SR-1 (1.9.101.1658). The release includes the following major changes:
- New: Flat File Source component will now use configured THUNK_COLUMN column length as default for all dynamic columns.
- New: Improved handling of dynamic columns in the JavaScript component.
- New: Support for Oracle Source component in SQL Server 2019.
- Fixed: Connection exhaustion because of resource leak in the system code, causing unexplained process slowdown (Thank you, Jake).
- Fixed: Failed with error "Not Found" when trying to overwrite an existing file.
- Fixed: 'Create remote directory' action in File Transfer Task will now avoid the creation of folders with same name.
- Fixed: Incorrect variable replacement in JSON.
- Fixed: Disabled various destructive commands in the script editor.
- Fixed: Improved memory consumption and management.
- Fixed: Removed not needed exception popup dialog because the error is already reported in the log.
- Fixed: Failed to retrieve "Saved Reports" resource from US-hosted service (Thank you, Hardik).
- Fixed: Failed with error "The request signature we calculated does not match the signature you provided. Check your key and signing method." (Thank you, Will).
- Fixed: If record processing failed, the composite data became misaligned from the current main record (Thank you, Andrei).
- Fixed: Failed with error "Object reference not set to an instance of an object" when processing 'ItemFulfillment' record (Thank you, Amol).
- Fixed: The bulk initialization statement was needlessly retrieving rows, slowing the process (Thank you, Irawan).
- Fixed: Failed to retrieve data from 'Billable Usage' resource (Thank you, Anna).
- Fixed: Disabled the default .NET forward-slash (/) and dot (.) unescape because it breaks connectivity to resources with such characters in use.
- Fixed: Custom -> 'Init from JSON' action didn't create a proper composite element definition.
- Fixed: MALFORMED_QUERY error in design mode when using aggregate query with LIMIT clause.
- Fixed: Failed with error "INVALID_TYPE: sObject type '...__r' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names." when trying to use relationship fields in SOQL statement (Thank you, Imran).
- Fixed: Failed with error "Object reference not set to an instance of an object" when trying to open dialog in Visual Studio 2019.
- Fixed: Failed to delete file with ampersand (&) special symbol in the name when using File Transfer Task (Thank you, Nandu).
