Known Issues · Einstein Analytics - Data Integration
Summer '20 - Creating a dataset from a Salesforce report fails with "Failed to fetch" error
Einstein Analytics - Data Integration , Operational Analytics - Reports , Summer 20
A known issue is causing a "failed to fetch" error when creating a dataset from a Salesforce report in Analytics Studio. This impacts the "Create > Dataset" flow when "A Salesforce Report" is chosen as the source. It does not impact the Trend functionality when accessed from a report directly.
In Review ·Reported By 3 ·Updated 2 days ago
Analytics - Recipe fails with "failed to create KeyValueType list" or "context cancelled" error
Einstein Analytics - Data Integration
A known issue is causing Recipes to fail to run with a message like the following: DataflowInstance [03C...] cancelled. Something went wrong while executing the ConvertToEdgemart node: failed to create KeyValueType list: schema (JSON) contains 2 'dataset.field_name' fields This may also manifest...
In Review ·Reported By 1 ·Updated 2 days ago
Einstein Analytics - Data Integration
Deploying a recipe that overwrites an existing recipe that has been scheduled does not unschedule the "old" recipe version, resulting in a "ghost" job that continues to run.
Scheduled - Summer '20 Patch 13.0 ·Reported By 5 ·Updated 3 days ago
Packaging , Einstein Analytics - Apps , Einstein Analytics - Data Integration
In orgs on the Summer '20 major Salesforce release, we are seeing similar errors to the below when uninstalling a package with a field included on a dataset Error: 1802406352-20360380 (894020651)
In Review ·Reported By 0 ·Updated 3 days ago
Dataset creation doesn't displayed the fields when "Report Event" object is selected
Einstein Analytics - Data Integration
Some objects such as "ReportEvent" and possibly some other Event Monitoring objects can't be added via Dataset Editor.
In Review ·Reported By 5 ·Updated 4 days ago
Einstein Analytics - Data Integration
When a dataflow, data sync, recipe, or external data job causes an environment to exceed its designated row limit, the job will appear to complete successfully but will fail to create or update its datasets. This can cause Einstein Analytics assets to return stale data or return one of the following...
Scheduled - Winter '21 ·Reported By 6 ·Updated 5 days ago
Analytics - Placeholder datasets appear in Search, cause error on Explore and Edit
Einstein Analytics - Data Integration
When a dataflow is updated or a change set/package is deployed, placeholder datasets are created. These datasets are metadata containers that do not have any data in them. These placeholders should not be visible in the UI, though they are visible in REST API. A known issue is allowing these placeholder...
In Review ·Reported By 1 ·Updated 5 days ago
Adoption App Dataset "DatasetLinkageEA" does not shows up data.
Einstein Analytics - Apps , Einstein Analytics - Data Integration
Adoption App Dataset "DatasetLinkageEA" does not shows up data. Sometimes DatasetLinkageEA dataset doesn't get refreshed and due to which Dashboard does not shows up data.
In Review ·Reported By 17 ·Updated 6 days ago
Einstein Analytics - Data Integration
In Summer '20 release environments, opening or adding a digest node to a dataflow via the dataflow editor and clicking on "Connection Name" results in the following error: "Sorry to interrupt This page has an error. You might just need to refresh it. [Error on parameter connector: java://java.l...
Release In Progress - Summer '20 Patch 10.1 ·Reported By 16 ·Updated 6 days ago
Trend in Analytics jobs intermittently fail with "Unable to write ReportInstance to EdgeMart" error
Einstein Analytics - Data Integration , Operational Analytics - Reports
Dataflow jobs for trended Salesforce reports may sporadically fail with an error message: "Something went wrong while executing the run_report node: Unable to write ReportInstance to EdgeMart.: Request body, *goSFDCapi.SfdcRestApiRequest, is not seekable. Cannot retry this 500 response"
In Review ·Reported By 8 ·Updated 9 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.
