Workfront Planning Fusion API Limitations

Planning API: Field Search and Mapping Limitations

There is no straightforward way to search or filter fields by name in the Planning API. Field IDs are not exposed in the Workfront UI, requiring additional API calls just to identify them. Mapping a field ID to its record type then requires chaining multiple searches, when this should ideally be handled in a single call.

Planning API: Create/Read/Update

From a Fusion developer perspective, it would be beneficial to support full programmatic create, read, update, and delete operations for record types and their fields. It would also be valuable to officially support patching individual record options. While we were able to accomplish this through an undocumented approach, having it formally available in the public API would significantly improve reliability and long‑term supportability.