Salesforce Einstein Analytics Connector Release Notes - Mule 3
Support Category: Select
Anypoint Connector for Salesforce Analytics Cloud enables you to connect to the Salesforce Analytics Cloud app using the Salesforce External Data API. The connector exposes convenient methods for creating and populating data sets into Salesforce Analytics Cloud system.
2.4.1
2.3.1
April 12, 2019
Compatibility
The Salesforce Analytics Cloud connector is compatible with:
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
External Data API |
v43.0 |
Fixed Issues
The Salesforce Analytics feature that uploads parts concurrently has issues when INVALID_SESSION_ID is received - Using the connector with the Batch Module was not working well when a connection issue appeared as the connector was not able to handle reconnection. This is now fixed. (SE-9555)
2.2.1
2.2.0
February 20, 2018
This release adds new features.
Compatibility
The Salesforce Analytics Cloud connector is compatible with:
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
External Data API |
v36.0 |
Features
-
Added support to allow wildcardmetadata/*.json for OAuth 2.0 JWT Bearer and OAuth 2.0 SAML Bearer.
A wildcard can now be used for the Metadata File Name field when configuring the connector’s Global Basic authentication.
-
Added support to disable session invalidation.
The authentication configuration now lets you disable session invalidation by checking the Disable session invalidation checkbox.
2.1.1
January 11, 2018
Compatibility
The Salesforce Analytics Cloud connector is compatible with:
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
External Data API |
v36.0 |
Fixed Issues
-
Fixed exception message when TLS version is not supported.
The error message "Failed logging in into Salesforce system" was not reflecting the root cause of TLS version not supported.
-
Record duplication while using connector concurrently.
-
Added metadata fields:
-
canTruncateValue - Indicates whether to truncate a value when the value exceeds the precision. The default is true. canTruncateValue Boolean No: if true, truncates the value. If false, the row is rejected.
Example:
"canTruncateValue": true
-
decimalSeparator - For numeric fields only. The character that separates digits in a decimal number. Can be used to handle international number formats where the decimal separator is “,”. The default is “.”.
Example:
decimalSeparator String No "decimalSeparator": ","
-
isYearEndFiscalYear - For date fields only. Indicates whether the fiscal year is the year in which the fiscal year ends or begins. Because the fiscal year can start in one isYearEndFiscalYear Boolean No calendar year and end in another, specify which year to use for the fiscal year. If true, then the fiscal year is the year in which the fiscal year ends. The default is true. If false, then the fiscal year is the year in which the fiscal year begins.
Example:
"isYearEndFiscalYear": true
- This field is relevant only when fiscalMonthOffset is greater than 0. -
firstDayOfWeek - For date fields only. The first day of the week for the calendar year and, if applicable, fiscal year. Use 0 to set the first day to be Sunday, 1 to set firstDayOfWeek Number No the first day to be Monday, and so on. Use -1 to set the first day to be January 1. The default is -1.
Example:
"firstDayOfWeek": 0
- See also Date Handling in Datasets. -
isSkipped - Indicates whether to skip the field when the data is uploaded. Example: isSkipped Boolean No "isSkipped": true
-
-
Made security token field optional for basic authentication.
The connector was enforcing the use of a security token even though it was optional.
2.1.0
October 5, 2016
Compatibility
The Salesforce Analytics Cloud connector is compatible with:
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
External Data API |
v36.0 |
2.0.3
2.0.1
2.0.0
August 28, 2015
Compatibility
The Salesforce Analytics Cloud connector is compatible with:
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
External Data API |
v34.0 |
Note that this is a major version release which breaks backwards compatibility.
Features
-
Added new field "Operation" on "Create data set"/"Upload external data into new data set and start processing" operations which provides the ability to choose the operation executed against the data set. Accepted values: OVERWRITE, APPEND, UPSERT, DELETE.
-
Added new field "Notification Sent" on "Create data set"/"Upload external data into new data set and start processing" operations which provides the ability to choose when to get email notifications based on processing results. Accepted values: ALWAYS, FAILURES, WARNINGS, NEVER.
-
Added new field "Notification Email" on "Create data set"/"Upload external data into new data set and start processing" operations which provides the possibility to choose the email where notifications to be sent.
Fixed Issues
-
Added "Authorization URL" to "Basic Authentication" configuration in order to provide the ability to change login server. So now you can point the connector to a Salesforce environment of your choosing
-
Added "Token Endpoint" to "OAuth 2.0 SAML Bearer"/"OAuth 2.0 JWT Bearer" configurations in order to give the ability to change the token provider server.
-
Removed support for multiple formats of metadata file, so removed "Metadata File Type" from all the configurations.
-
Added a warning message for when the data provided to a batch commit step is bigger than the maximum allowed size (10 MB) to upload one chunk into the Analytics Cloud using the InsightsExternalDataPart objects. This will help the user to maximize performance of the connector. For more details, please refer to the API documentation Add the Data.
1.1.0
April 17, 2015
Compatibility
The Salesforce Analytics Cloud connector is compatible with:
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
External Data API |
v31.0 |
Features
-
Create data set - This operation provides the ability to create a schema in the Analytics cloud for data ingestion
-
Upload external data - This operation uploads the data into an existing data set in the Analytics Cloud.
-
Start processing data - This operation communicates with Salesforce to start the processing of uploaded data to enable data visualizations and other features within Wave.
-
Upload external data into new data set and start processing - This operation combines the aforementioned three operations into a single operation.