Help Article:
The WHY:
Report accuracy
-
With min/max and required population at creation
Integration consistency
-
With data types that match the connected system
Flexible granularity
-
With project or task-level values and in-line edit
New capabilities:
Population at the project or task level
-
Datatypes beyond strings (dates, drop-downs, links, numbers, boolean toggles, etc)
Validation for minimum or maximum values
-
Requirement for population during creation
Initial Workflow
-
Create new custom fields in company settings
-
Drag the sort order of how custom fields appear according the sequence you prefer them to appear in the edit pane
-
Populate values in edit drawer or in-line on global projects table
Backwards compatibility:
UI: Legacy labels and values have been auto-migrated to the new format as of a few minutes ago
-
You can pick up where they left off with confidence all values will persist
API: Integration Builder connectors will continue to run without interruption
-
The new data type and validation properties are optional
-
The new task-level custom field endpoint is available now for custom actions until the connector is updated this week
Reports: Legacy datasets are still available but their values will no longer update
-
The new dataset will be available NEXT WEEK but Report Builder users will need to manually swap out the legacy dataset for the new one
Next steps:
Merge Tags: These will soon be auto-migrated just like legacy custom fields
-
Later in June we will switch the merge tag selection UI to check the custom fields table for labels that are public / externally visible
-
Then another script will set object type = project, data type = text, and visibility = public external
-
Until then, the legacy merge tag and new custom field global management screen will continue to be used in tandem