Increase Calculated Field Limits in Planning
Context
An enterprise customer implementing Adobe Workfront Planning encountered a platform‑imposed limit of 20 calculated fields per record type while trying to add a few additional calculated fields to support new teams. They asked whether this restriction could be overridden.
Steps taken
Support investigated and confirmed that Workfront Planning currently enforces a hard limit of 20 calculated fields per record type. This limit is part of the product’s performance guardrails and cannot be changed or increased within an individual customer environment.
Business impact
The customer is using a single, centrally governed workspace to maintain consistent intake, taxonomy, and reporting across multiple lines of business. Calculated fields are a core component of their sizing, normalization, and reporting logic. The 20‑field cap forces them to:
- Remove or consolidate existing calculations
- Introduce manual workarounds
- Fragment their data model across multiple record types or workspaces
This undermines their goal of using Planning as a centralized, enterprise‑grade planning system, slows down their rollout, and risks reduced data quality, higher operational overhead, and limited scalability as more teams onboard.
The ask
- Why does the 20‑field limit on calculated fields exist in Workfront Planning?
- Is there any plan or timeline to increase or remove this cap?
- Given that this limitation has surfaced for multiple organizations, what is the recommended enterprise design pattern or workaround when the need clearly exceeds 20 calculated fields per record type?