Indexes allow us to determine the headings which is displayed whenever data record types are listed.
Also, If you wish to find an item using a Get statement with any clauses attached to it, the fields will need to be indexed. I.E. If you wish to find all the people who's first name is "John" then the element First Name must be an index on the Person type. Please note: The number of indexes on an object is limited - there’s a limit of 10 string indexes (sIndex01 – sIndex10) 5 date indexes and 5 number indexes.
Types of Indexes
Elements in the Normal Display are the elements that are searchable through SQL Query
Elements in List Display defines the elements which will be displayed when that type is shown in a List or in a Group.
Elements in the Relationship Display define the elements which will be displayed when the type is present in a relationship field on a Type or a Form and various other places within the application as shown below.
Long String Index is an application level index created by combining element-value pairs into one string.
For example, an object with the following fields and values respectively can be turned into a string:
Name: John Doe Age: 28 Company: Pengower
Long String Index: "$Name=John Doe=Name$$Age=28=Age$$Company=Pengower=Company$
Using Indexes in scripts allows elements to be searchable through SQL inquiries which are only used in Action Scripts.
Using Indexes in Lists allows the display of selected elements as column headers. Elements as column headers can be used as criteria for searching objects.
Adding and Editing Indexes
To learn how to add and edit Indexes, visit the tutorial on How to add indexes to a Type
You can see how Indexes are added and used in this video below: