Compound fields are useful for a variety of situations. They can be used to summarize key data for reports, create unique identifiers based on account numbers or associated records, or provide a clear title with which to view data. The following are a few examples of how compound fields can be used to customize and enhance the user experience.
In this first example, the administrator has created a new compound field, Record Title. This field is a compound of the Contract Type and Company Name. By creating a descriptive and standardized title for the record in this way, the admin assures that all records will have a uniform label to identify them.
In this next example, the compound field is leveraged to support existing business practices. The Compound ID field created here includes the department ID, company ID, contract type ID, and a unique identifier. Keep in mind, the delimiter between values is customizable, so these values could have just as easily been a dash or a space, or nothing at all!
Compound fields are not particular about whether a field they use is a string. Here we see an example of how a table uses an integer field (ID) and a string field (Task Summary) to create a Task Title field.
The result of this compound field is a string. This is important to keep in mind when sorting records, since a record called “1034 – Order parts” will come before “98 – Hire new engineer.” It is always important to be aware of the ways in which strings and integers behave differently.
Let us know how you use compound fields to represent your records!