A saved search is one end user's copy of a search view, edited for the needs of that user and saved under a name that is assigned by the user. Saved searches do not have i18n keys, so there is no action to be taken by the solution developer with regard to localization. However, there is some localization behavior that should be understood. Under one uncommon and specific set of circumstances, a saved search can behave slightly differently from other features, with respect to localization.

The labels of criteria and result fields are always obtained, when possible, from the original search view that underlies the saved search. However, since the end user can remove results and criteria, and add brand-new results and criteria, there can be elements in the saved search that are not found in the original search view. In this case, one of two things will happen:

•If the element is a custom field, its label will be obtained from the object definition.

•If the element is not a custom field, the label used will be the one that was in existence at the time the search was saved. Even if that end user is now using a different locale, the label in the saved search will reflect the locale at the time the search was saved.