Indexing Fields

Index your custom fields to speed up the performance of saved searches in the different object work areas. The global search isn't affected. To ensure optimal search performance, index only the most frequently searched custom fields.

What can you do with indexing?

• You can index only these types of fields:

  • Currency

  • Number

  • Percentage

  • Text

• Once you index a field, you can't un-index it.

• You can index fields either when you first create them, or when you later edit them. But, there are different limits in place when creating fields vs. editing them.

Let's look at the index limits when creating a field:

• For standard objects, you can index two text fields and three number fields (shared among number, percentage, and currency fields) during creation.

• For custom parent objects, you can index 10 text fields and 15 number fields (shared among number, percentage, and currency fields) during creation.

  For custom child objects, you can index 10 text fields and 14 number fields during creation.

There is a separate index limit in place when editing a field. You can index fields after creating them, whether for standard or custom objects, but you are limited to indexing a maximum of 5 fields across your entire implementation. This is in addition to the fields that you can index per object, during creation.

Note: You can index a greater number of fields for certain Oracle Sales standard objects. The exceptions are listed in the following table.

Index Limits for Oracle Sales Standard Objects

Oracle Sales Standard Object	Indexing Options
Account	10 number fields 10 text fields 10 case-insensitive text fields (UPPER)
Account custom child	15 number fields 10 text fields
Contact	10 number fields 10 text fields 10 case-insensitive text fields (UPPER)
Contact custom child	15 number fields 10 text fields
Opportunity	2 text fields 8 number fields
Sales Lead	2 text fields 16 number fields
Service Request	2 text fields 1 number field

Things to consider when indexing fields:

• Dynamic choice list fields and relationships automatically use 1 indexed number field.

• If all indexed number fields are already taken, then Application Composer uses a non-indexed number field.

• If a tab or BI analysis is based off a dynamic choice list field or other relationship, then create that relationship first to ensure you obtain an indexed number field. This ensures optimal performance for your tab or analysis.