Bi Admin Guide Setup
Bi Admin Guide Setup
PREVIEW
Note: This release is in preview. Features described in this document don’t become generally available
until the latest general availability date that Salesforce announces for this release. Before then, and where @salesforcedocs
features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within Last updated: April 21, 2023
any particular time frame or at all. Make your purchase decisions only on the basis of generally available
products and features.
© Copyright 2000–2023 Salesforce, Inc. All rights reserved. Salesforce is a registered trademark of Salesforce, Inc., as are other
names and marks. Other marks appearing herein may be trademarks of their respective owners.
CONTENTS
Important:
• CRM Analytics license data storage limits are contractual, not technical. Licensee agrees to strictly monitor its total number of
data rows.
• If you purchased an CRM Analytics Growth license before October 20, 2015 with Analytics Cloud Builder or Analytics Cloud
Explorer permission set licenses: Read Set up the CRM Analytics Platform With Licenses Purchased Before October 20, 2015. If
you’re migrating users from Builder or Explorer licenses to the new CRM Analytics Growth license: See Migrating From CRM
Analytics Licenses Purchased Before 10/20/2015 to New CRM Analytics Platform Licenses before you start the setup process
for those users.
• If you disable CRM Analytics, user permissions are removed from each defined permission set. If you re-enable CRM Analytics
later, you must define the permission sets again.
1
Analytics Platform Setup Guide Learn About Internal Analytics Users
• CRM Analytics Plus Admin enables all permissions required to administer the CRM Analytics platform and Einstein Discovery,
including permissions to create and manage CRM Analytics templated apps and Apps.
• CRM Analytics Plus User enables all permissions required to use the CRM Analytics platform, Einstein Discovery, and CRM Analytics
templated apps and Apps.
Basic setup involves choosing and assigning the prebuilt permission sets. To create your own custom CRM Analytics permission sets,
use advanced setup.
When you assign any CRM Analytics permission set to users in your org, Salesforce auto-assigns the CRM Analytics Growth permission
set license to that user.
Note: For efficiency, you can assign a permission set to groups of users. You can also assign multiple permission sets to a user.
You can assign a CRM Analytics permission set license along with any of the following Salesforce user licenses:
• Lightning Platform (app subscription)
• Lightning Platform (one app)
• Full CRM
• Salesforce Platform
• Salesforce Platform One
Important: Because Analytics requires the Integration User and Security User to access Salesforce data and preview recipe changes
to data, do not delete either of these users.
SEE ALSO:
Control Access to Salesforce Objects and Fields
Set Up Dataset Security to Control Access to Rows
2
Analytics Platform Setup Guide Basic CRM Analytics Platform Setup
4. Click Manage Assignments. The next page shows the users already assigned the selected permission set.
5. To see all the users in your org click Add Assignments.
6. Select one or more users by checking the box next to their name in the left-hand column.
3
Analytics Platform Setup Guide Advanced CRM Analytics Platform Setup
7. Click Assign.
You see a page that tells you if the permission set has been assigned. If permission set didn’t succeed for one or more users, Salesforce
tells you why. You can fix the problem and try again.
Tip: For best results, follow the steps in the order shown.
Learn About CRM Analytics Permission Set Licenses and User Permissions
When you create your own CRM Analytics permission sets, you start by selecting the CRM Analytics Growth permission set license instead
of using the prebuilt permission sets. The permission set license includes the user permissions required to explore data with and manage
the CRM Analytics platform.
• Each CRM Analytics platform user needs a CRM Analytics Growth permission set license to use the CRM Analytics platform. Creating
a permission set and assigning it to a user auto-assigns the CRM Analytics platform permission set license to that user. You can also
manually assign permission set licenses to users.
• Experience Cloud site users need a CRM Analytics for Communities permission set license to view CRM Analytics apps shared via
dashboards embedded in sites or Visualforce pages.
The CRM Analytics Growth permission set license enables the following permissions, except Manage CRM Analytics Private Assets.
Access Analytics SAQL Editor (Pilot Feature) This user permission is no longer used and will be removed in a future release.
Add CRM Analytics Remote Connections Add connections to access data from external data sources.
Adoption Analytics Templates and Apps Create and use apps based on the Adoption Analytics template.
Create CRM Analytics Apps Create, edit, delete, and share CRM Analytics applications.
Create and Edit CRM Analytics Dashboards Create, edit, and delete CRM Analytics dashboards.
Download CRM Analytics Data Download screenshots and data in tabular format through the CRM Analytics
user interface.
Edit CRM Analytics Dataflows Edit, delete, and use remote connections; add and remove connected objects;
run and schedule data sync; create, edit, delete, run, schedule, and monitor
dataflows and recipes. Use discretion when assigning this user permission
because it enables access to all Salesforce object data to which the Integration
User has access. See Salesforce Data Access in CRM Analytics.
Edit Dataset Recipes Create, edit, and run recipes to create datasets. Monitor dataflow and system
jobs in the monitor. Doesn’t enable editing security predicates in existing
recipes.
Manage CRM Analytics Private Assets Delete datasets from another user’s My Private App. See Delete a Dataset.
4
Analytics Platform Setup Guide Advanced CRM Analytics Platform Setup
Manage CRM Analytics Access all CRM Analytics features. Provides CRM Analytics administrator-level
capabilities.
Manage CRM Analytics Custom Maps Add, edit, and delete maps, and upload geoJSON files.
Manage CRM Analytics Templated Apps Create and manage apps based on CRM Analytics Templates. Edit CRM Analytics
dataflows. Edit recipes. Monitor dataflow and system jobs in the monitor. Some
templates require extra permissions. See the help for each template.
Trend Report Data in CRM Analytics Trend the data of a report with a CRM Analytics dataflow.
Upload External Data to CRM Analytics Upload external data to CRM Analytics to create a dataset. Monitor dataflow
and system jobs in the monitor.
Use CRM Analytics Open CRM Analytics; run CRM Analytics apps to which you have access; view
their datasets, lenses, and dashboards; and create and edit lenses.
Use CRM Analytics Templated Apps Use apps based on CRM Analytics Templates. Can also create, edit, and delete
CRM Analytics dashboards. Some templates require extra permissions. See the
help for each template.
Note: When you create permission sets for CRM Analytics users, selecting any CRM Analytics permission automatically enables
the “Use CRM Analytics” permission as well. Also, the type of access granted on an app controls the actions that can be performed
on its datasets, lenses, and dashboards. For example, if a user has the “Use CRM Analytics” permission, the user must also have
Viewer access on an app to view its datasets, lenses, and dashboards.
The CRM Analytics for Communities permission set license enables the “View CRM Analytics on Experience Cloud pages” permission.
That permission enables external users to view CRM Analytics dashboards embedded in their Experience Cloud sites. See Enable CRM
Analytics for Experience Cloud Sites on page 9.
5
Analytics Platform Setup Guide Advanced CRM Analytics Platform Setup
Note:
• Customers who purchased CRM Analytics before October 20, 2015: See Set up the CRM Analytics Platform With Licenses
Purchased Before October 20, 2015 before following the instructions here.
• The Manage CRM Analytics permission set enables the equivalent functionality provided by the previous Analytics Builder
license (purchased before October 20, 2015). If you have a Builder license or you’re migrating to the current CRM Analytics
platform license, follow these steps to create a permission set with the same functionality.
• The View CRM Analytics permission set enables the equivalent functionality provided by the previous CRM Analytics Explorer
license (purchased before October 20, 2015). If you have an Explorer license or you’re migrating to the current CRM Analytics
platform license, follow these steps to create a permission set with the same functionality.
1. In the Setup menu, click Users | Permission Sets and then click New.
6
Analytics Platform Setup Guide Advanced CRM Analytics Platform Setup
2. Enter Manage CRM Analytics or View CRM Analytics in the Label field, as appropriate. This automatically creates
the API name as well. You can change it if you like, but it can’t include spaces, end with an underscore, or have two consecutive
underscores.
3. For License, select the license to associate with this permission set.
When you select a specific permission set license, any user assigned to the permission set is auto-assigned the permission set license.
If you select --None--, you must manually assign the permission set license to users before you can add them to the new permission
set.
4. Click Save. The Permission Set Overview page shows the new permission set. Now add user permissions to the set.
5. Click System Permissions to open the list of user permissions enabled by the CRM Analytics license. Then click Edit.
6. Do one of the following.
• If you're creating the Manage CRM Analytics permission set, select "Manage CRM Analytics" user permissions and click Save
then Save again to confirm settings. You’ve successfully created a permission set that enables access to all CRM Analytics features.
You don’t have to select any of the other individual permissions. Assign this permission set sparingly because it provides access
to all CRM Analytics features, many of which are inappropriate for most analytics users.
• If you're creating the View CRM Analytics permission set, select "Use CRM Analytics" and "Upload External Data to CRM Analytics"
user permissions and click Save. You’ve successfully created a permission set that enables a user to view the CRM Analytics
datasets, lenses, and dashboards that they have permission to view, and to upload data files from outside Salesforce.
7. You can now assign your new permission set to users, which is covered in Assign Permission Sets to Users. Repeat these steps for
every user in your organization who requires access to CRM Analytics.
8. Enable CRM Analytics
a. Go to Salesforce Setup and enter Analytics in the Quick Find / Search field.
b. Select Getting Started.
c. Click Enable CRM Analytics.
7
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
2. Lightning Assets
a. From Setup, enter Reports in the Quick Find box, then select Reports and Dashboards Settings.
b. Select Show preview thumbnails for reports and Lightning dashboards.
c. Click Save.
8
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
USER PERMISSIONS
To view visualizations:
• Use CRM Analytics
9
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
USER PERMISSIONS
To modify settings:
• Manage CRM Analytics
10
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
USER PERMISSIONS
To modify settings:
• Manage CRM Analytics
Note: To subscribe to tables and receive email with table data in attached .csv files, users
need both the Download CRM Analytics Data and the Subscribe to CRM Analytics Assets USER PERMISSIONS
permissions.
To modify settings:
• Manage CRM Analytics
11
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
3. Click Done, then click the Salesforce Analytics App Package and then View Components.
USER PERMISSIONS
4. Select iOS or Android. To configure policies and other settings, click Edit. When you’re finished,
save your changes. To install and configure
For more information about Connected App settings, see Edit a Connected App. Connected App:
• Manage CRM Analytics
5. If you want to disable sharing options for mobile users, click New in the Custom Attributes
section.
All sharing options are enabled by default. To disable an option, add its attribute key and enter “false” for the attribute value.
See the table for the supported attribute keys.
12
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
Note: To apply custom attributes to connected users, you can revoke them and ask them to reconnect.
6. To view and control how mobile clients connect to your CRM Analytics-enabled org, from Setup, in the Quick Find box, enter
Connected Apps, and then select Connect Apps OAuth Usage.
You can block user sessions, revoke individual users, and drill in to user details. For more information, see Monitoring Usage for a
Connected App.
Note: For certificate-based authentication, users must set their desktop browsers to allow cookies.
For extra security, use Mobile Device Management (MDM) with the option to show only authorized hosts. The "OnlyShowAuthorizedHosts"
key allows you to hide the “Add New Account” plus sign in the mobile app. For more information, see Using MDM with Salesforce Mobile
SDK Apps.
• The administrator can implement object-level and field-level security to control access to Salesforce data. For example, the administrator
can restrict access to prevent the dataflow from loading sensitive Salesforce data into datasets. This document describes how CRM
Analytics uses object-level and field-level security on Salesforce data and how to configure permissions on Salesforce objects and
fields.
• Dataset owners can implement row-level security on each dataset that they create to restrict access to it’s records. If a dataset does
not have row-level security, users who have access to the dataset can view all records. This document describes how to configure
row-level security on datasets and provides some sample implementations based on datasets created from Salesforce data and
external data.
• App owners, administrators, and users granted manager access to an app control access to datasets, lenses, and dashboards within
apps. This document describes the different levels of access for apps and how to share datasets, lenses, dashboards in an app with
other users.
13
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
Note: CRM Analytics supports security predicates, a robust row-level security feature that enables you to model many different
types of access controls on datasets. Also, CRM Analytics supports sharing inheritance, to synchronize with sharing that’s
configured in Salesforce, subject to certain limitations. If you use sharing inheritance, you must also set a security predicate to
take over in situations when sharing settings can’t be honored.
For complete information about implementing CRM Analytics security, see CRM Analytics Security Implementation Guide.
Important: Because CRM Analytics requires the Integration User and Security User to access Salesforce data, do not delete either
of these users.
14
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
Note: You can’t change the permissions on standard fields of the User object.
9. Verify that the Integration User or Security User has the right permissions on fields of the objects.
15
Analytics Platform Setup Guide Complete Setting up the CRM Analytics Platform
For CRM Analytics Encryption to function properly, you must define IP ranges for the Analytics Cloud Integration and Analytics Cloud
Security user profiles as documented in, Best Practices: Manage Integration and Security Users in CRM Analytics. Also, add designated
Salesforce IPs to your allowlist, Salesforce IP Addresses and Domains to Allow.
Features
Key export, Bring Your Own Key, key rotation, key revocation, and key import are available.
All CRM Analytics features are supported, with the following exceptions:
• Pre-existing data is not encrypted.
• Data that was in CRM Analytics before encryption was enabled is not encrypted.
• If pre-existing data is imported from Salesforce objects through the dataflow, the data becomes encrypted on the next dataflow
run.
• Other pre-existing data (such as CSV data) must be reimported to become encrypted.
• Although pre-existing data is not encrypted, it is still accessible and fully functional in its unencrypted state when encryption is
enabled.
Frequently Asked Questions
Is data encrypted in transit? Yes. However, encryption in transit is different from encryption at rest. This feature covers encryption at
rest.
Can CRM Analytics bring in data encrypted with Shield Platform Encryption? Yes. CRM Analytics reads platform encrypted data
in the same way that any user reads platform encrypted data. The data is then written and encrypted in CRM Analytics. It is not required
that data be encrypted with Shield Platform Encryption to be encrypted in CRM Analytics. It is only required that a Tenant Secret exist
for the org.
Can I mask my data? No. Masking data is not currently available and it does not fall under the CRM Analytics scope.
Are the keys different for Shield Platform Encryption and CRM Analytics Encryption? Yes, although Shield and CRM Analytics
use the same key management technology, they use different keys.
Do mobile dashboards still work with encryption? Yes. All CRM Analytics functionality, including support for mobile devices, works
with encryption enabled. All data stored on mobile (mainly JSON code and thumbnails) is AES 256 encrypted.
Is there any impact on application performance? The CRM Analytics Encryption solution is designed to have at most a minimal
performance impact on your CRM Analytics application experience.
16
Analytics Platform Setup Guide Set Up the Analytics Platform with Licenses Purchased Before
October 20, 2015
Note: This information applies only to customers who purchased Analytics licenses before October 20, 2015, and continue to
use the Analytics Cloud Builder or Analytics Cloud Explorer licenses after that without migrating to the new Analytics Growth
license. If you purchased Analytics on or after October 20, 2015, go to Set Up the CRM Analytics Platform.
Important: If you’re migrating from the previous Analytics Cloud Builder or Analytics Cloud Explorer platform licenses to the
single-user Sales Analytics Apps license, read Migrating From Analytics Licenses Purchased Before 10/20/2015 to New Analytics
Platform Licenses.
“Create Analytics Apps” Builder only Creating and sharing Analytics applications.
17
Analytics Platform Setup Guide Migrating From CRM Analytics Licenses Purchased Before
10/20/2015 to New CRM Analytics Platform Licenses
“Use Analytics” Builder and Explorer Using Analytics, and viewing the datasets,
lenses, and dashboards that the user has
permission to view. Automatically enabled
when you select any other Analytics
permission.
Note: When you create permission sets for Analytics users, selecting any of the other CRM Analytics permissions automatically
enables the “Use Analytics” permission.
You can assign previous Analytics permission set licenses along with any of the following Salesforce user licenses:
• Lightning Platform (app subscription)
• Lightning Platform (one app)
• Full CRM
• Salesforce Platform
• Salesforce Platform One
SEE ALSO:
Migrating From CRM Analytics Licenses Purchased Before 10/20/2015 to New CRM Analytics Platform Licenses
• Analytics Cloud Builder license users. Users who access CRM Analytics with the Analytics Available with CRM
Cloud Builder license should be able to continue to use the CRM Analytics platform without Analytics, which is available
any additional setup. The Builder license is simply renamed CRM Analytics Growth, and you’ll for an extra cost in
see that permission set license in Salesforce Setup. Enterprise, Performance,
and Unlimited Editions. Also
• Analytics Cloud Explorer license users. During the new license provisioning process,
available in Developer
Salesforce may remove the Analytics Cloud Explorer license from your org. If that’s the case,
Edition.
you’ll see the new CRM Analytics Growth license instead of the Explorer license and you have
to set up users with that license. If the Explorer permission set license is still visible, you do not
have to repeat the setup process for Explorer users.
18
Analytics Platform Setup Guide CRM Analytics Limits
If users in your organization require you to set them up with the new CRM Analytics Growth license—even if they used CRM Analytics
with a previous license—follow the steps in CRM Analytics Platform Setup on page 1. You need to assign them the new permission
set license, create one or more new permission sets, and assign the permission sets to users.
Limit Value
Maximum concurrent CRM Analytics API calls per org 100
Maximum CRM Analytics API calls per user per hour 10,000
CRM Analytics for Financial Services Cloud license baseline row 25 million
allocation
CRM Analytics for Health Cloud license baseline row allocation 25 million
Your org’s total row storage limit is a combination of your org’s active licenses. For example:
CRM Analytics Plus License
• If your org has a CRM Analytics Plus license and adds the Event Monitoring license, your total row limit becomes 10.05 billion.
(10 billion plus 50 million)
• If your org has a CRM Analytics Plus license and adds the Additional Data Rows license, your total row limit becomes 10.1 billion.
(10 billion plus 100 million)
• If your org has a CRM Analytics Plus license and adds two more Data Rows licenses, your total row limit becomes 10.2 billion.
(10 billion plus (2 X 100 million)
19
Analytics Platform Setup Guide CRM Analytics Limits
Note: The CRM Analytics Plus license already includes a Sales Analytics and Service Analytics license, so your total row allocation
remains 10 billion. Similarly, the CRM Analytics Growth license already includes a Sales Analytics and Service Analytics license,
so your total row allocation remains 100 million. In these situations, if your org obtains another Sales Analytics or Services
Analytics license, your org row limit increases by 25 million for each app obtained.
Dataset Row Limits
Each dataset supports up to 2 billion rows. If your Salesforce org has less than 2 billion allocated rows, then each dataset supports
up to your org’s allocated rows.
Dataset Field Limits
Limit Value
Maximum number of fields in a dataset 5,000 (including up to 1,000 date fields)
Maximum number of decimal places for each value in a numeric 17 decimal places
field in a dataset (overflow limit)
When a value exceeds the maximum number of decimal places,
it overflows. Both 100,000,000,000,000,000 and
10,000,000,000,000,000.0 overflow because they use more than
17 decimal places. A number also overflows if it’s greater (or less)
than the maximum (or minimum) supported value.
36,028,797,018,963,968 overflows because its value is greater
than 36,028,797,018,963,967. -36,028,797,018,963,968 overflows
because it’s less than -36,028,797,018,963,967.
When a number overflows, the resulting behavior in CRM
Analytics is unpredictable. Sometimes CRM Analytics throws an
error. Sometimes it replaces a numeric value with a null value.
And sometimes mathematical calculations, such as sums or
averages, return incorrect results. Occasionally, CRM Analytics
handles numbers up to 19 digits without overflowing because
they are within the maximum value for a 64-bit signed integer
(263 - 1). But numbers of these lengths aren’t guaranteed to
process.
As a best practice, stick with numbers that are 17 decimal places
or fewer. If numbers that would overflow are necessary, setting
lower precision and scale on the dataset containing the large
numbers sometimes prevents overflow.
20
Analytics Platform Setup Guide CRM Analytics Limits
Limit Value
Maximum value for each numeric field in a dataset, including 36,028,797,018,963,967
decimal places For example, if three decimal places are used, the maximum
value is 36,028,797,018,963.967
Limit Value
Maximum size per staged dataset 2 billion rows (but not exceeding org's max staged data rows)
Maximum staged data rows per org Org max rows divided by two. For example, an org with a limit of
1,200,000,000 (1.2 billion) rows for final datasets by default has
600,000,000 (600 million) rows for staging datasets.
Days retained 30
Limit Value
Maximum number of concurrent data sync runs 3
Maximum number of objects that can be enabled for data sync, 100
including local and remote objects
Maximum amount of time each data sync job can run for local 24 hours
objects
Maximum amount of time each data sync job can run for remote 12 hours
objects
Data sync limits for each job: Up to 100,000 rows or 500 MB per object, whichever limit is
• Marketo Connector (Beta) reached first
• NetSuite Connector
• Teradata Connector (Beta)
• Zendesk Connector
Data sync limits for each job: Up to 1 million rows or 1 GB per object, whichever limit is reached
• Analytics MuleSoft Microsoft SQL Server Connector first
21
Analytics Platform Setup Guide CRM Analytics Limits
Limit Value
• Analytics MuleSoft MySQL Connector
• Analytics MuleSoft Oracle Connector
Data sync limits for each job: Up to 10 million rows or 5 GB per object, whichever limit is
• AWS RDS Oracle Connector reached first
Data sync limits for each job*: Up to 20 million rows or 10 GB per object, whichever limit is
• AWS RDS Aurora MySQL Connector reached first
Data sync limits for each job*: Up to 100 million rows or 50 GB per object, whichever limit is
• Amazon Redshift Connector reached first
• Amazon S3 Connector
• Customer 360 Global Profile Data Connector (Beta)
• Google BigQuery for Legacy SQL Connector
• Google BigQuery Standard SQL Connector
• Heroku Postgres Connector
• Microsoft Azure SQL Database Connector
• Snowflake Input Connector
*When using these connectors, Salesforce Government Cloud org data is protected in transit with advanced encryption and can
sync up to 10 million rows or 5 GB for each connected object, whichever limit is reached first.
22
Analytics Platform Setup Guide CRM Analytics Limits
Note: When using a Salesforce local input connection, CRM Analytics bulk API usage doesn’t count towards Salesforce bulk
API limits. Use of the external Salesforce connection and output connection impacts your limits.
The dataflow submits a separate bulk API call to extract data from each Salesforce object. The dataflow uses a batch size of
100,000–250,000, depending on whether the dataflow or the bulk API chunks the data. As a result, to extract 1 million rows
from an object, the dataflow creates 4–10 batches.
Limit Value
Maximum number of recipes 1,000
Maximum number of concurrent dataflow runs 2 for production orgs with the CRM Analytics Plus platform license
1 for production orgs with the CRM Analytics Growth platform
license or sandbox orgs
Maximum number of Data Prep previews per hour per user 4,000
Timeout for data load jobs (dataflows, CSV uploads, recipes, and 5 minutes
data sync) that have been scheduled but not executed
Limit Value
Maximum number of trended datasets per user 5
Maximum number of rows in the report to be trended 500,000 for admins, 100,000 for non-admins
Maximum monthly number of rows for all snapshots per org 40 million
23
Analytics Platform Setup Guide CRM Analytics Limits
Limit Value
Maximum file size per external data uploads 40 GB
Maximum file size for all external data uploads in a rolling 24-hour 50 GB
period
Limit Value
Maximum data written to Salesforce 100 MB per run of a recipe per output connector
100 MB per rolling 24-hour period
Maximum data written to Azure Data Lake 100 MB per run of a recipe per output connector
100 MB per rolling 24-hour period
Maximum data written to Amazon S3 10 GB, or 10 million rows of data per run of a recipe per output
connector
50 GB, or 50 million rows per rolling 24-hour period (combined*)
Maximum data written to Snowflake through recipe or sync out 10 GB, or 10 million rows of data per run of a recipe per output
connector
50 GB, or 50 million rows per rolling 24-hour period (combined*)
Maximum data written to Tableau Online 1 GB, or 1 million rows of data per run of a recipe per output
connector
1 GB, or 1 million rows per rolling 24-hour period
*The limit for Snowflake Output or sync out and Amazon S3 Output connectors is a combined 50 GB, or 50 million rows per rolling
24-hour period. For example, if you push 40 GB of data from CRM Analytics to Snowflake, then 10 GB of allotted data remains to
push to Amazon S3.
Story Creation and Prediction Limits
For limits on story creation and predictions, see Einstein Discovery Limits.
24
Analytics Platform Setup Guide CRM Analytics Limits
Limit Value
Maximum number of characters in a security predicate 5,000
Limit Value
Maximum number of data rows 250,000
Limit Value
Maximum JSON file size per dashboard 4 MB
Default number of rows in a compare table 2000 (To set a different value, use the SAQL limit statement)
Default number of rows in a values table 100 (To set a different value, use the SAQL limit statement)
25
Analytics Platform Setup Guide CRM Analytics Limitations
Limit Value
Maximum concurrent Analytics Download API calls per user 3
Update Schedule
All customers receive CRM Analytics updates on the same schedule, regardless of instance.
Field-Level Security
Field-level security isn’t available for external data that is uploaded via files. Field-level security that was implemented in the original
database or Salesforce object isn’t preserved when the data is loaded into a CRM Analytics dataset. For more information, see the CRM
Analytics Security Implementation Guide.
Set Salesforce field-level security to enable the CRM Analytics Integration User to see all fields used in your app—default fields and those
selected in the configuration wizard. Integration users run the dataflow, and if they don’t have proper field-level security permissions,
the dataflow fails.
26
Analytics Platform Setup Guide CRM Analytics Limitations
Explorer Limitations
You can't filter or group by the hour, minute, or second components of a date field.
You can’t filter on values containing HTMLEncoded text.
Because dates are sorted lexicographically, changing the date format also changes the sort order.
• There are two requirements if you choose to import Campaigns data to Sales Analytics using the configuration wizard.
1. At least one opportunity must be connected to a campaign.
27
Analytics Platform Setup Guide CRM Analytics Limitations
• There are two requirements if you choose to import opportunity record types to Sales Analytics using the configuration wizard.
1. At least one opportunity record type must be defined.
2. The opportunity record type must be connected to at least one opportunity.
Object support Standard and custom objects Standard objects Standard and custom objects
28
Analytics Platform Setup Guide CRM Analytics Limitations
29
Analytics Platform Setup Guide CRM Analytics Limitations
30
Analytics Platform Setup Guide CRM Analytics Limitations
31