In this article
| Table of Contents | ||||
|---|---|---|---|---|
|
...
| Expand |
|---|
This section tracks the changes made during the iterative pushes to the UAT server and the GA release. The following is the release schedule:
The SnapLogic GA release build on the production server is also deployed on the UAT server. |
| Info |
|---|
Important
|
...
| 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 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 Success Manager (CSM) or SnapLogic Support to subscribe to Microsoft Dynamics 365 for Sales Snap Pack. |
Snap Pack | Date of Update | Snap Pack Version | Updates | |||||
|---|---|---|---|---|---|---|---|---|
| 428patches15638 | 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. | ||||||
| 428patches15236 |
| ||||||
| 428patches15459 |
| ||||||
| 428patches15101 | 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. | ||||||
| 428patches (main101) | Fixed the Auto Refresh Token issue in the SharePoint Online Account. | ||||||
| 428patches15172 | 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. | ||||||
| 428patches14649 | 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.
| ||||||
| 428patches15200 | Enhanced the JWT Generate Snap to include the
| ||||||
| 428patches15290 |
| ||||||
| 428patches14755 | Enhanced the Spreadsheet Browser Snap with the Fetch Mode dropdown list to fetch the spreadsheets and worksheets.
| ||||||
| 428patches14812 | Fixed an issue with the Email Sender Snap where SMB files were attached to an e-mail causing the Snaps to fail with a | ||||||
| 428patches15219 | Updates in the MS Dynamics 365 for Sales Create and MS Dynamics 365 for Sales Upsert Snaps:
| ||||||
| 428patches15216 | Added the AWS S3 Dynamic account for Parquet Reader and Parquet Writer Snaps. | ||||||
| 428patches15026 | 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. | ||||||
| 428patches15164 | Fixed an issue with the Azure SQL - Update Snap where the Snap failed with an | ||||||
| 428patches14919 |
| ||||||
| 428patches15114 | Fixed an issue with the Azure SQL - Bulk Load Snap where the decimal values lost precision when they were inserted into the database. | ||||||
| 428patches14774 | Fixed an issue in the SQS Consumer Snap where the Snap took longer time to process the messages when the Client-side buffering checkbox was selected. | ||||||
| 428patches14736 | Fixed an issue in the File Writer, S3 File Writer, and ZipFile Write Snaps where the Snaps failed with | ||||||
| 428patches14290 | Enhanced the Workday Cancel Snap with retry mechanism fields.
| ||||||
| 428patches14904 | 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. | ||||||
| 428patches14370 | Fixed an issue with the XML Generator Snap, where the Snap failed with an invalid | ||||||
| 428patches14332 | Upgraded the Splunk library to version 1.6.5.0 to fix an issue with the Splunk Search Snap, where the Snap displayed a | ||||||
| 428patches14355 | Fixed an issue with Salesforce Snaps where the Service Version could not be retrieved from SFDC due to a blocked URL, failing the Snap execution. | ||||||
| 428patches14743 |
|
...
Expressions used in the Mapper Snap, downstream of any Snowflake Snap, that evaluate to very large values such as EXP(900) are displayed in the input/output previews as
Infinity. However, you can see the exact values in the validation previews; hence, ignore this error.Google BigQuery does not support very large exponential values—larger than EXP(700). So, while displaying values of such high exponential order in the validation preview, the Google BigQuery Execute Snap routes to the error view, and displays the
"Data conversion failed for field f0_(FLOAT) of value Infinity."error.
The Snap also displays empty output in the preview, which is not expected.The metadata output in the second output preview is not displayed in table format when your target database is AWS Athena.
The suggestions list is not populated for Table name field when your target database is AWS Athena.
This Snap does not support using ABFS protocol with a Windows-based Snaplex.
When you use special characters, such as
ðø©¢¾A²½µ®÷¶þ~for Source and Target directory and filenames, the Snap fails and results in the following error as the special characters are not supported.Error: Illegal character in fragment at index 71: abfs://bigdataqa@bigdataqassl.dfs.core.windows.net/simplechar/owner!@#$^&()_¢äâêîôûñç¡¿ÉÙËǨ°¸ðø©¢¾A²½µ®§÷¶þ~.json,The format:
abfs(s)://filesystem@accountname.endpoint/<path>for file path for Source and Target fields does not work as this URL syntax is not supported. The file protocol must begin withabfs(s):///,else the container, account name, and endpoint are interpolated into the URL at runtime, which results in the following error.Error: Unsupported protocol or URL syntax error in abfs(s)://filesystem@accountname.endpoint/<path>,
Workaround: Use the supported file protocol and correct URL syntax.
The Bulk Lead Upsert and Bulk Lead Extract Snaps do not display valid error messages when you provide large, empty, null, string, or other invalid values (timeout value that is less, for instance, 10) in the Timeout (seconds) and Number of Retries fields. These Snaps work successfully and do not display any error message when you pass large input data through the Pipeline parameters. However, when you pass large input static data in these fields the Snap displays an error.
The Bulk Lead Upsert Snap fails upon parsing data greater than 100000 records.
Snowflake OAuth2 Account has a maximum validity of the Refresh tokens as 90 days (7776000 seconds). The Snowflake platform does not allow you to get a new refresh token when refreshing the access token for the Snowflake External OAuth.
Solution: To get a new token after every 90 days you must re authorize your Snowflake account for the token to be valid for the next 90 days. We recommend you to set the
oauth_refresh_token_validityto 7776000 seconds as shown below when creating the Security Integration in Snowflake.Code Block language sql alter integration <integration name> set oauth_refresh_token_validity = 7776000;
...