Can I define data format of a custom field?

You can set a format specifier for custom card fields that require a set format of data, like a time-stamp or a zipcode. Doing so will speed up typing and unify the way your team members enter data into that field.

You can define the format in any way you like and use the following placeholder characters:

• 0 as a placeholder for any digit
• a as a placeholder for any letter
• * as a placeholder for any character

So if you have a custom field for tracking the order number, and the order number always starts with ORD, followed by three digits, and ends with Z, you can use the following format specifier for that: ORD000Z

Optional values should be enclosed in square brackets. For example, [0]aa defines a format for fields that start with an optional digit followed by two letters.

Predefined values that should be automatically added to the input should be enclosed in curly brackets. For example, with a format specifier like {+1} 000, once you begin typing in a number, a +1 text will be automatically prepended to the field.

If there is a placeholder character you want to display in the custom field, prepend it with ` in your format definition.

Common examples of format specifiers include:

• a phone number: +{1}(000)000-0000
• time value: 00:00
• zip code: 00000
• deal value: $00000.00
• time-stamp: 00:00:00:00
• order number [AAA]000-000

Below is an example of a custom phone number and deal value data format. When a team member proceeds to add this information for this specific task, they will be able to do so using the format suggested automatically by the placeholder text, preventing them from having to type any repetitive characters on each of the cards.