Custom fields are incredibly powerful and allow you to add additional information into Planhat that is important for your team. Custom fields can be added to almost any data model in Planhat e.g. Companies, End Users, Licenses, NRR, Opportunities, Tasks, Conversations and many more 🚀!
Good examples of bringing in custom data include creating custom fields on Company Profiles so you can bring in data that you have already collected in your CRM. You can also create value-adding CS fields such as "Next Key Objective", "Potential Risks" and "Customer Goals". If you're ready to start creating your own range of custom fields, grab a coffee and read on ☕.
How to Add Custom Data Fields
There are a couple of different ways that you can add custom fields in Planhat:
1. Via the "Data" Global Tool
Navigate to the "Data" Global Tool in the top-left of your Planhat tenant. (Note that typically, only admins have access to this. Permissions are set within Roles.)
Ensure your desired model is selected in the list on the left-hand side, and that the "Fields" tab is selected
Click the orange "+ New Field" button in the top right
Click the image to view it enlarged
Enter the details of your field in the form
2. Add Custom Fields via API
Custom fields can also be created by using our API. Check out our API documentation here.
📌 Important to note:
The gear symbol next to a field means that this is a system field available as default in Planhat, and it cannot be removed. The pencil/ruler icon means it's a custom field that you have added.
The "Hide this field" option will hide the field from the interface, but you can still use the field in your search queries or in filters.
Custom Field Data Types
There are several different data types to choose from when creating a custom field. We have listed all of the data types below with a brief description 👍.
📌 Important to note: It's NOT possible to edit the field type after a custom field has been created (even if you delete all the data related to the custom field). If you want to change the field type, you'll need to delete the custom field and recreate it with the new field type (you will lose any data that's stored in the field).