Known Issues · Einstein Analytics - Data Integration
Dataflow and/or Datasync did not run at scheduled time SFDC_LOCAL connection did not run at scheduled time
In Review ·Reported By 8 ·Updated Yesterday
An error is received when navigating to a required field with no value. This error is not announced by screenreader
In Review ·Reported By 2 ·Updated Yesterday
A known issue is causing some multivalue fields to behave erratically in datasets generated from recipes. Most commonly, this results in the multivalue field contents being truncated to 255 characters (including the multivalueSeparator character between each value). This may manifest as disruption...
In Review ·Reported By 1 ·Updated Yesterday
Segmentation filters that use "&" and probably other special characters too do not work for segmentation filters in Recipes. These do work for the Prediction API
In Review ·Reported By 0 ·Updated Yesterday
A dataset created with a data recipe only shows in the dataset details, define security predicate and not define sharing source
In Review ·Reported By 1 ·Updated 2 days ago
Recipe joins involving Account with sharing inheritance enabled may cause the recipe to fail with an error containing "... Something went wrong while executing the SelectSharingRulesForAccountFrom-ConvertToEdgemart node: Row-level sharing source information for Account is missing...."
In Review ·Reported By 0 ·Updated 2 days ago
When "Enable Data Sync and Connections" is enabled a SFDC_Local Connector is created for replicating your local Salesforce Data. After the Spring '20 release, admins have the option to create additional SFDC_Local connections to strategically manage when your Salesforce data syncs to Einstein Analytics...
Fixed - Spring '20 Patch 16.0 ·Reported By 8 ·Updated 4 days ago
Since Spring 20 release, some dataflows may fail with error: "Something went wrong while executing the test node: error reading from block: EOF "
Fixed - Spring '20 Patch 8.0 ·Reported By 6 ·Updated 4 days ago
A known issue is causing recipes in Einstein Analytics to fail if they include a field that has a precision greater than 32,000. This may result in an error message like the following: Something went wrong while executing the ConvertToEdgemart node: context canceled
Fixed - Summer '20 ·Reported By 5 ·Updated 4 days ago
Dataflow jobs digesting tables from a Redshift Remote Connection may occasionally pull zero rows into the related Connected Dataset.
Fixed - Summer '20 Patch 7.0 ·Reported By 4 ·Updated 4 days ago
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.