Table of Contents | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Snap Pack | Date of Update | Snap Pack Version | Updates | |||||
---|---|---|---|---|---|---|---|---|
| 434patches22837 | Updated the input and output schema for the Marketo Snaps. | ||||||
| 434patches22758 | Fixed an issue with the SQL Server Stored Procedure and Table List Snaps that caused no retries to be executed even though the user had selected a number of retries in the UI when a custom JDBC driver was used. | ||||||
| 434patches22787 | Fixed an issue with the Oracle-Bulk Load Snap that was not resilient to the errors previously when trying to auto-discover the existing SQLLDR utility paths in the node. The Snap is now robust to those errors. | ||||||
| 434patches22736 |
| ||||||
| 434patches22639 | The JSON key field in the Binary Google Service Account supports JSON strings. You can upload the JSON key either from SLDB or dynamically pass the value using a pipeline parameter or access values from Secrets Manager. | ||||||
| 434patches22705 | Fixed an issue with the JSON Splitter Snap that caused the pipeline to terminate with excessive memory usage on the Snaplex node after the | ||||||
| 434patches22662 |
| ||||||
| 434patches22631 | Fixed an issue with the HTTP Client Snap that displayed incorrect cookie information, with a null value in the cookies when you have duplicate cookies in the header. The Snap now displays the cookie information correctly. | ||||||
| 434patches22576 | Fixed an issue with the Pipeline Execute Snap that caused a null pointer exception during the retry when the input view was a Binary type. Retry is not supported for a Binary input view with this Snap. | ||||||
| 434patches22620 | Fixed an issue with the Azure Active Directory Create Entry Snap that caused it to fail with a cast error when a boolean value was entered in a field where expressions were enabled. | ||||||
| 434patches22655 | Fixed an issue with the SOAP Execute Snap that caused it to be unable to parse some WSDL files. | ||||||
| 434patches22579 | Improved the SQL Server Bulk Load Snap to help reduce the chance of causing a deadlock error. | ||||||
| 434patches22600 |
| ||||||
| 434patches22537 | Improved the Salesforce Bulk Upsert Snap error messages by limiting the length of the reason displayed with the error. | ||||||
| 434patches22601 |
| ||||||
| 434patches22562 | Fixed an issue with the Google Analytics 4 Create Report and Create Realtime Report Snaps that improperly rounded off decimal data. You can now view the precise value in the report. |
...
Upgraded the JDBC driver support for Snowflake to snowflake-jdbc-3.13.33.jar.
Updated the ELT Snowflake Account to append or replace (if it exists) the connection parameter
application
in its JDBC URL with the valueSnapLogic_iPaaS
.This change complies with Snowflake’s latest Connection Identifier standard.
...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Breaking ChangeWith the new support for LDAP authentication to HashiCorp Vaults, the Snaplex node configuration file Action needed: You must update each of your existing Snaplex node configuration files to include this key-value pair: |
...
Breaking Changes
Pipelines that use the default Microsoft JDBC Driver in the SQL server accounts might be impacted after the upgrade because the latest driver is backward-incompatible. For more details, refer to the FAQ for Upgrading to SQL Server JDBC Driver 12.2.0. To prevent an impact to your accounts, reconfigure the URL properties field in account settings as follows: trustServerCertificate = true
Upcoming
We plan to upgrade the Oracle Snap Pack to use the latest 19c JDBC JAR file (19.19.0.0 as of November 8, 2023).
Pipelines that use the default JDBC driver in the Oracle server accounts might be impacted after the driver upgrade because the latest driver is backward-incompatible. We will soon communicate how to reconfigure to prevent accounts from being impacted.
Pipelines that do not use the default driver (bundled with the Oracle Snap Pack) are not impacted.
New Snaps
The following new Snaps and Snap Packs are available with the August 2023 stable distribution. To access these new Snaps, enable the auto-upgrade mode or manually upgrade your Snaplex. Snaplexes are upgraded automatically 4 weeks after GA.
Introduced the Microsoft Dynamics 365 Business Central Snap Pack:
Dynamics 365 Business Central Create: Creates user records in the Business Central application for a specific entity.
Dynamics 365 Business Central Delete: Deletes user data from a specific entity.
Dynamics 365 Business Central Read: Reads user details for a specific entity.
Dynamics 365 Business Central Search: Searches for the required data for a specific entity
Dynamics 365 Business Central Update: Updates the user records for a specific entity.
Dynamics 365 Business Central OAuth2 Account: Connects the Snap with the Microsoft Dynamics 365 Business Central application that requires OAuth2 authorization.
Dynamics 365 Business Central Access Token Account: Connects the Business Central Snaps with data sources that dynamically use the Access Token.
Introduced the Google Analytics 4 Snap Pack:
Create Realtime Report: Creates a customized report of your Google Analytics real-time event data.
Create Report: Creates a customized report of your Google Analytics event data.
Google Service Account: Authenticates and authorizes applications or services to access Google APIs.
Introduced the following Snaps:
Google BigQuery Upsert (Streaming): This Google BigQuery Snap enables you to perform bulk update and insert operations into a BigQuery table from existing tables or any input data stream.
HDFS Delete: This Hadoop Snap provides a streamlined and efficient method for deleting files from Azure Data Lake Storage.
PGP Sign: This Binary Snap enables you to use PGP to sign a file digitally without encrypting the file.
SuccessFactors Read Advanced: This SAP SuccessFactors Snap enables you to read objects recursively for objects containing links to traverse through the tree structure.
Transform Snap Pack:
GeoJSON Parser: Parses geospatial data from binary data input and outputs the contents as a GeoJSON document downstream.
WKT Parser: Parses geospatial data from binary data input and outputs the contents as a WKT (Well-known Text) document downstream.
...
All the database Execute Snaps now include a new Query type field. When Auto is selected, the Snap automatically determines the query type.
Added new SFTP (Secure File Transfer Protocol) settings in the
global.properties
file:sftpSessionTimeoutSec
cacheSftpSessions
The Anaplan Action Snap now supports Data errors/warnings for better output handling. The reason for the process failure also displays now.
All the Anaplan Snaps now display the status code as part of the error message if the error status code is available as part of Anaplan API response.
The Aggregate, Group By Fields, Group By N, Join, Sort, and Unique Snaps from the Transform Snap Pack now include new fields to improve memory management.
The Amazon S3 Snaps automatically detect the Maximum session duration value for the Cross-Account IAM role (1 through 12 hours). The Snaps round down the value to the nearest hour. So, if the Snap administrator sets the Maximum session duration at 3 hours and 45 minutes, the Snaps read it as 3 hours. The Snaps also refresh the session before the session expires. However, the automatic session refresh does not support very large file uploads or downloads that takes longer than the maximum session duration.
The Decrypt Field and Encrypt Field Snaps from the Transform Snap Pack now support CTR (Counter mode) for the AES (Advanced Encryption Standard) block cipher algorithm.
The Decrypt Field Snap now supports the decryption of various encrypted fields by providing a valid decryption key.
The Deduplicate Snap now manages memory efficiently and eliminates out-of-memory crashes using the following fields:
Minimum memory (MB)
Minimum free disk space (MB)
The pagination feature implemented for the ABFS protocol in the Hadoop Directory Browser Snap enables the Snap to return all the output documents as expected.
The SSH fields in the Generic Database account are now expression enabled.
The LDAP Search and LDAP Lookup Snaps now support a string representation for binary attributes with the Include string representation for binary attributes checkbox.
Microsoft Dynamics 365 for Sales Snap Pack:
The Dynamics 365 for Sales Snaps includes a new Enable continue on error checkbox to allow the Snap to continue executing the remaining batch requests, even if the previous request does not execute.
The Dynamics365 for Sales Update Snap performs the update operation as expected when the Batch size is more than 1, and the Snap successfully executes when the batch size is 1.
The NetSuite Snap Pack now supports the Customer-Subsidiary and the Vendor-Subsidiary relationship Object types.
Note: NetSuite's application requires the Oneworld extension for using these subsidiary relationships, and Snap integration must use WSDL 2019_1 or later versions.The PGP Encrypt Snap now includes an Encryption key ID field, which allows you to specify the key ID for encrypting the data. If you do not specify an encryption key ID, the Snap uses the first key in the public key (master key).
The Redshift-Bulk Load and Redshift-Bulk Upsert Snaps now support expression enablers for the Additional options field, which enables you to use parameters.
The Snowflake - Bulk Load and Snowflake - Bulk Upsert Snaps are enhanced with the Flush chunk size (in bytes) field. When using internal staging, data is written to a temporary chunk file. When the file exceeds the specified size, it is copied to the Snowflake stage and deleted.
SQL Server Snap Pack:
This Snap Pack is upgraded to the Microsoft JDBC Driver
12.2.0.jre11
for SQL Server. Existing pipelines that do not use the default driver (bundled with the SQL Server Snap Pack) are not impacted. If you want to use NTLM or other authentications with the latest default driver (where the DLL file is mandatory), then you must copy the DLL file to the Snaplex path. Learn more about the SQL Server driver upgrade: FAQ for Upgrading to SQL Server JDBC Driver 12.2.0.The SQL Server Stored Procedure and SQL Server Table List Snaps now support the retry functionality.
...
Fixed the pagination issue for the Deals Entity in the HubSpot Read Snap.
Fixed an issue in the SAP S/4HANA Create Snap where a few fields were missing in the schema population in the Mapper Snap.
Fixed the encoding issue in the SAP S/4HANA Update Snap.
Fixed an issue with the Send Email Snap where attachments larger than 3 MB were not getting attached to the sent email messages.
...
Starting from version 433patches21482, the PGP Encrypt Snap does not support encryption with an expired key. To ensure continued support for encryption, we highly recommend that you renew your PGP key before it expires or extend the expiration date of your PGP key.
Starting from version 433patches22343, the Vertica-Bulk Load Snap displays no output in the output view when the Snap receives no input.
With the
433patches21307
, pagination evaluation in the HTTP Client Snap occurs before sending the output to the output view. Therefore, ifsnap.out.totalCount
is part of the Has next or any other pagination properties, the Snap will not include the count in the output corresponding to the request that produced the output document.
Known Issues
For the Binary and Email Snap Packs, SFTP connections might experience connectivity issues because of the removal of some deprecated algorithms. To add these connections back, refer to Configuration Settings for Snaps for details.
If you use the PostgreSQL driver (
org.postgresql.Driver
) with the Redshift Snap Pack, it could result in errors if the data type provided to the Snap does not match the data type in the Redshift table schema. Either use the Redshift driver (com.amazon.redshift.jdbc42.Driver
) or use the correct data type in the input document to resolve these errors.The Send Email Snap might fail because of a
429
error response from the Graph API endpoint.For Ultra Tasks using a continuous data flow design for polling with a Pipeline Execute Snap, the parent pipeline does not receive the document from the child pipeline, and the polling message is not generated for downstream Snaps.
The GeoJSON Parser and WKT Parser Snaps accept only
application/zip
orapplication/gml+xml; charset=utf-8
as a file input stream.
However, the output content type from the File Reader Snap isbinary/octet
when the input file is read from SLDB.Workaround: To read an input file (ZIP or GML) from SLDB, use the Mapper Snap to change the content type from
binary/octet
to one of the following:ZIP file: Change the content type to
application/zip
.GML file: Change the content type to
application/gml+xml; charset=utf-8
.
When you provide a custom JAR file in the Oracle Thin Account or the Oracle Thin Dynamic Account, the Oracle Stored Procedure Snap fails with the following errors:
"com.snaplogic.snap.api.SnapDataException: object is not an instance of declaring class"
"Class oracle.sql.BLOB cannot be cast to class java.sql.Struct"
(For BLOB data type)"class oracle.sql.CLOB cannot be cast to class java.sql.Struct"
(For CLOB data type)Workaround: Remove the custom jar file from the account and retry.
...
Enhanced the following Custom Snap documents by adding missing information, improving clarity in field descriptions, and implementing the latest UI changes:
SnapGPT
: Launched SnapGPT, an AI-driven platform that lets you generate your pipelines using simple text prompts. Learn more.
...