The Raw object data store option provides an alternative to the standard Vault object data store method which can improve performance and consistency if used with an appropriate record set. This option is best used for objects with large numbers of small records, frequent object record creation or editing, and predictable viewing patterns.
Admins should carefully consider whether to use the Raw data store setting for a given object, as raw objects have limitations not encountered with standard Vault objects. Use the below guidelines to help determine whether your object should use the Raw data store option.
The Raw data store option provides improved performance and consistency in cases where:
- The object has a large number of records, in the millions. Raw objects can have up to one billion records.
- Records are frequently created or updated, and often through integrations.
- Users filtering and viewing the object records do so with predictable methods.
The Raw data store option is unlikely to be advantageous in cases where:
- Object fields and other configuration attributes are expected to change frequently.
- Admins and users require advanced features of the standard Vault object search, such as faceted field filters or record-level security.
- Users require a high degree of flexibility in searching records.
Note: Raw objects were previously known as high volume objects (HVO).
Raw Object Limitations
Admins should understand the limitations of raw objects before configuring them.
Search
Users viewing raw object tabs can use the Vault search bar to find records. Raw objects also support case-sensitive record filtering. In order to use filtering on custom fields, an Admin must first define a custom filtering index. Without custom indexes, users may experience slow responses or timeouts when filtering. Additionally, searches on raw objects cannot return more than 1,000 records.
You cannot search for records in related object sections or in the advanced record Search dialog for raw objects.
Modification
If a raw object has more than 10,000 records, the following modifications require the use of configuration packages or developer tools:
- Add or remove fields
- Change the length of any variable-length field, such as Text, Long Text, or Rich Text
- Create indexes
- Enable lifecycles
- Enable or disable object types
Learn more about how to modify raw objects.
Note: During the week of a General Release, we may lock raw objects from configuration changes if they are impacted by data model changes in the release. We recommend not making configuration changes to environments during this week as this can also increase the downtime.
Multi-Value Picklists
Raw objects support a maximum of two (2) multi-value picklists.
You cannot use the contains operator in filters on multi-value picklist fields in raw objects.
Reporting
You can use lookup fields on raw objects within standard and Multi-Pass reports. Reporting functionalities such as conditional fields, grouping results, and sorting are available for these reports. However, filters are not supported for non-searchable lookup fields in standard reports.