Other than it’s ‘not possible’ in NXT, I can’t seem to find an explanation as to why we can’t create formula fields on system objects...specifically Call to Action. Our use case is one we initially had in SFDC...a formula field (boolean) to tell us if a CTA was closed within 30 days or not. This is an essential metric for our teams. The work-around during our transition was to build a completely separate data design and calculate the field there, but it’s far from ideal.
- The data design is a separate object, so now we can’t include this field in our API pushing the rest of our CTA data to our warehouse. They now have to recreate a formula field there (more work, and room for error)
- We’ve started pushing users to take advantage of self service analytics and have our CTA object as one thing they can build reports on. Now, we have to give them access to the 2nd data design object just for these few formula fields. It’s confusing for end users and makes taking advantage of this new reporting functionality challenging.
- We can’t just ‘add a column’ to existing reports if end users ask for one of these formula fields to be included after the fact. It means rebuilding reports, readding to dashboards, remapping global filters just to surface this info.
Is there any further discussion as to why this functionality isn’t possible? Is it a roadmap item or never going to be available? At minimum, it would be nice if we could use a rule to load these fields...but formulas directly on the object would be ideal.