Current Limitations for Summary Search Custom Fields

This topic describes the current limitations for summary search custom fields. For general information, see Creating Custom Fields with Values Derived from Summary Search Results.

• Custom field values from summary search results are never stored. Field values are always calculated dynamically at runtime. A user may be able to edit values, depending on the display options set for the custom field, but the edited values aren't stored. Also, because its values aren't stored, the field can't be used in search results, including lists based on saved searches.

• If you have a use case for running a saved search on a formula field where the value isn't stored, there's an alternative solution available. For more information, see Running a Saved Search on a Formula Field Where the Value is Not Stored (SuiteAnswers ID: 1017388).

• Calculated values for summary search custom fields can vary for users with various permissions. Summary search results are rolled up for the records to which the current user has access. Because users with various permissions can have access to different sets of records, the calculated value of the field can vary per user.

Related Topics

• Creating Custom Fields with Values Derived from Summary Search Results
• Steps for Creating a Summary Search Custom Field
• Custom Fields that Support Summary Search Derived Values
• Custom Field Data Types that Support Summary Search Derived Values
• Example Summary Search Custom Field

General Notices