GA: Saturday, – Snaplex version: main-11177 - 4.28 GA (Recommended)
The SnapLogic GA release build on the production server is also deployed on the UAT server.
Info
Important
Per theSnapLogic Release Process, all remaining Snaplex instances across Orgs are auto-upgraded to the recommended version (main-11177 - 4.28 GA) at 9 p.m. PT on Saturday, . Orgs migrated to the 4.28 GA version prior to the auto-upgrade are not impacted. The Snaplex upgrade process also upgrades the Java version to the latest version. After the upgrade, the Java version of your Cloudplex nodes may not be the same as your FeedMaster nodes. However, this does not impact the operations of your SnapLogic instance. We will be fixing this issue in a subsequent release.
To use the new SnapLogic features and Snaps in the 4.28 release, ensure that your Snaplex nodes are upgraded to the main-11177 - 4.28 GA (Recommended) version.
This 4.28 release includes the patches deployed to SnapLogic after the 4.27 release, as listed in the4.27 Dot Releasessection.
4.28 Dot Releases
SnapLogic Studio
Date of Update
Update
Removed Last Execution and Last Status in the Execution Overview to improve performance.
Snaps
Note
Use Microsoft Dynamics 365 for Sales Snap Pack in lieu of Microsoft Dynamics CRM Snap Pack
As Microsoft has deprecated its following offerings, the Dynamics CRM Snaps configured with the Dynamics 365 Account For Online or Dynamics 365 Dynamic Account For Online fail with a Ws-Trust authentication error.
The Microsoft Dynamics CRM Snap Pack (CRM) will be deprecated in the upcoming August, 4.30 SnapLogic releaseafter the on-premise support is added in the Microsoft Dynamics 365 for SalesSnap Pack. If you are using the Dynamics 365 Online Accounts for Dynamics CRM Pipelines, we recommend that you immediately update these Pipelines and Accounts with Microsoft Dynamics 365 for Sales that uses the REST-based API (Web API) recommended by Microsoft.
Before you begin your migration, contact your Customer Support Success Manager (CSM) or SnapLogic Support to subscribe to Microsoft Dynamics 365 for Sales Snap Pack.
Fixed the issue with ELT Merge Into Snap where the Snap erroneously modified the target table column name when it contained the target table name, due to a misinterpretation of the target table name aliases.
The Snap displayed an incorrect resolution when the length of the value exceeded the value defined in a column.
The Snap failed with a NullPointer Exception when no value was provided for Error Limit field and Errorpercentage limit fields.
The Snap displayed an incorrect error message when S3 details were not provided.
Added the On Error dropdown list, where you can select an action to perform when the Snap encounters errors in a file.
Expand
title
Learn more:
On Error: Use this field to select an action to perform when the Snap encounters error in a file. The available actions are:
- ABORT_STATEMENT: Aborts the upsert action and displays an error.
- CONTINUE: Continues loading the file. The error is displayed in the output document.
- SKIP_FILE: Skips upserting the files that contain errors.
- SKIP_FILE_*error_limit*: Skips file when the number of errors in the file exceeds the number specified in the Error Limit field.
- SKIP_FILE_*error_percent_limit*%: Skips file when the percentage of errors in the file exceeds the percentage specified in the Error Percentage Limit field.
Default value:ABORT_STATEMENT Example:SKIP_FILE
Removed the Username field in the following accounts to allow reusing of accounts among different users:
Fixed an issue with Google BigQuery Execute Snap, where the Snap displayed 404 Job not found error when calling a procedure.
Fixed an issue with the Google BigQuery Bulk Load (Cloud Storage) Snap where the Snap failed, because the access token expired when it had to wait longer to execute. With this fix, the Snap is reloaded to get refreshed access token.
Fixed an issue with SQL Server - Execute Snap where the Pipeline was failing when there were consecutive execute Snaps with a procedure call, followed by select statements.
Fixed an issue that caused REST SSL accounts to fail when the username in the REST SSL Account was null and the Enhanced Encryption level was low, medium, or high.
Enhanced the SQL Server - Select and SQL Server - Lookup Snaps with Option for Unique Identifier Column that allows you to convert the case to lower or upper while displaying the Unique Identifier output (display) value.
Expand
title
Learn more:
Option for Unique Identifier Column: This field is applicable only when the Snap returns the unique identifier (GUID) in the output. The unique identifier is stored in the database using an internal format and when it is displayed in the output, it is converted to a string and gets displayed in upper case for HEX characters. Select either of the following options to change the case type. Available options are:
- Convert to lower case: Modifies the output string to lower case.
- Convert to upper case: Modifies the output string to upper case.
Default Value: Convert to lower case Example: Convert to upper case
Updated ELT SCD2 Snap to address different feature requests and issues raised by multiple customers. These changes provide more flexibility in configuring your SCD2 operations using this Snap.
Removed Check for nulls and duplicates in source field and added two dropdown lists - Null Value Behavior and Invalid Row Handling.
Fixed an issue with HTTP Router Snap where the Snap did not work as intended for a GET request that used a Cloud URL when the HTTP Router was the first Snap in the triggered task Pipeline.
Fixed an issue with the Azure SQL - Update Snap where the Snap failed with an Incorrect syntax error when a column in a table is of NVARCHAR, NCHAR, or NTEXT data type and this column is part of another NVARCHAR, NCHAR, or NTEXT data type column name and the update condition is specified as an expression.
Fixed an issue with the Directory Browser Snap where the Snap failed while parsing the value in the Amazon S3 client region.
Enhanced the File Writer Snap with the Prevent URL encoding checkbox to manage the URL encoding.
Expand
title
Learn more:
- Select this checkbox to prevent the encoding of the file path URL automatically. This allows the Snap to use the file path value as-is.
- Deselect this checkbox to automatically encode the characters in the File URL.
Fixed an issue with the ZipFile Write Snap where the Snap displayed a null pointer exception when the path in the upstream File Reader Snap started with "../".
Fixed an issue in the Binary Snaps (that support SMB file protocol), which displayed an SMB Mount error when trying to connect to Mount Share.
Fixed an issue with the File Writer Snap where the Snap did not display an error when an error occurred while writing a file.
Fixed an issue in the File Writer, S3 File Writer, and ZipFile Write Snaps where the Snaps failed with AccessControlListNotSupported error when using an external AWS account to write to the bucket if it has the bucket-owner-enforced setting enabled. With this fix, you can select the None option (the default value), from the AWS Canned ACL dropdown list, indicating that no Canned ACL request is set when writing a new file to prevent the error.
Fixed an issue with Kafka Snaps where the Snaps failed with null pointer exceptions when logging the cluster information with the controller’s identity not known.
Upgraded the Splunk library to version 1.6.5.0 to fix an issue with the Splunk Search Snap, where the Snap displayed a 401 Unauthorized access error despite entering valid credentials.
Fixed an issue with the Google BigQuery Execute Snap, where the Snap displayed an error when the input data contained a table having the record type column and its value was null.
Fixed an issue with the Google BigQuery Write Snap, when the input data contained complex data type columns (such as nested fields) and Create table if not present checkbox was selected.
Platform
As previously announced, SnapLogic has ceased support for Windows Server 2012 on , since this version did not support strong ciphers. Ensure that you upgrade your Groundplex instances to Windows 2016 or 2019.