Custom Properties in Custom Lists

Custom Properties allow you to add additional fields to your Custom List items beyond the basic value. This lets you store extra information like icons, colors, codes, or metadata alongside each list item.

Understanding Custom Properties

By default, each Custom List item has only a Value field—the text that appears when someone selects the item from a dropdown. Custom Properties let you add more data to each item.

Example Use Cases

  • Department List: Add a "Department Code" property (e.g., "SALES", "MKT", "ENG")
  • Status List: Add an "Icon" property to display different icons for each status
  • Region List: Add a "Timezone" property
  • Category List: Add a "Color" property for visual identification

Accessing Custom Properties

  1. Navigate to Admin → Custom Lists
  2. Click on the Custom List you want to modify
  3. Click the Custom Properties tab

Adding a Custom Property

  1. Click New in the Custom Properties tab
  2. Configure the property:
    • Title: The name of the property (e.g., "Department Code")
    • Data Type: The type of data (Plain Text, Number, etc.)
    • Required: Whether every list item must have this property
  3. Click Save

Using Custom Properties

Once you've added a Custom Property:

  1. Go to the List Items tab
  2. When adding or editing an item, you'll see fields for each Custom Property
  3. Fill in the property values for each item

Available Data Types

Custom Properties support various data types:

  • Plain Text: Simple text values
  • Number: Numeric values
  • Date: Date values
  • Boolean: Yes/No values

Important Notes

  • The main Value property cannot be edited or deleted—it's required for all Custom Lists
  • Adding a required property means you'll need to update existing items to include that property value
  • Custom Properties are optional for most use cases—only add them if you need extra data per item

Tips

  • Plan your Custom Properties before adding many list items
  • Use descriptive property names
  • Consider whether a property should be required before creating it
  • Keep the number of Custom Properties manageable—if you need many fields, consider whether a regular Data Collection might be more appropriate

Still need help? Contact Us Contact Us