You are here:
Limits and Considerations
As you create and work with offline briefcases, note these considerations and limits.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Type | Maximum Limit | Comment |
|---|---|---|
| Total active briefcases per org | 5 | |
| Total top-level object rules per briefcase | 10 | |
| Total object rules per briefcase, including top-level rules and related rules | 20 | |
| Total levels of hierarchy for related object rules | 6 | |
| Total custom metadata type rules per briefcase | 10 | |
| Total records per object | 50,000 | Object rules default to 500 records per object. |
| Total records that can be retrieved offline across active briefcases in an org | 50,000 per user | |
| Total filters per object | 10 | |
| Users per briefcase | Salesforce doesn’t limit the number of users per briefcase, but the number of records plus the number of assigned users does affect briefcase performance. |
Performance
- To optimize briefcase performance and obtain faster query results for records:
- Include fewer objects and fewer records in a briefcase.
- Reduce the number of records and add more filters on an object.
- Avoid using unindexed fields in filters.
- When selecting objects for a briefcase, Salesforce recommends that you apply at least 1 filter to each object for optimal performance.
- To optimize performance, only indexed fields are listed in the Order By dropdown list for record sort order.
- A custom or standard field in the Order By field can affect briefcase performance. To
optimize briefcase performance, select
Sysmodstamp.
Objects
- Unsupported
- ContentDocument
- ContentVersion
- KnowledgeArticle
- KnowledgeArticleVersion
- External objects
- Setup objects
- Supported
- Standard and custom objects that are customizable and layoutable
Filters
- When you apply filters to an object, you must enter a value for each field. You can’t save filters with missing values.
- An orange warning icon on a filter indicates an unindexed field. Unindexed fields can
affect briefcase performance. For more information, click the warning icon.
- A red error icon on a filter indicates an invalid value. To apply the filter, you must resolve invalid values. For more information, click the error icon.
Fields
- These filter fields aren’t supported: HTMLMULTILINETEXT, HTMLSTRINGPLUSCLOB, MULTILINETEXT, and STRINGPLUSCLOB.
- Compound fields aren't supported, but individual fields within the compound fields are.
- Briefcase Builder supports filtering and sorting by encrypted fields, but these field actions depend on the type of encryption used. The two types of encryption schemes are probabilistic and deterministic. Briefcase Builder doesn’t allow sorting by encrypted fields. But Briefcase Builder allows filtering by deterministically encrypted fields with the operator EQUALS.
- When filtering by formula fields, we recommend pairing your filter with at least one non-formula field for better performance. Depending on the number of records and the complexity of the formula, filtering exclusively by formula fields can result in long query times or errors.
Record Scope
For Record Scope, the default value is All Records. The value Assigned to Me is available only for the Service Appointment object.
Briefcase Assignment
For briefcase assignments, Briefcase Builder supports Standard, Partner, and Custom Portal Manager User types.
Person Account
The offline briefcase feature supports person accounts. Their fields are available as filters on the Account object.
Did this article solve your issue?
Let us know so we can improve!
