Robert Tullo - 2 months ago
Absolutely need more than one formula field. The simple workaround is that while we could create a column holding the value, that will probably be an unneccesary column for a large number of users. So that extra overhead on an object to support a few people is not a good design methodology. It would have a far better UX to build a specific report with the needed calculations for a given set of users.
Up the number of available row level formula fields or make it unlimited. Let the user determine what is an appropriate load time.
The Management :)
Mark Bohuslav - 2 months ago
They really need to up this limit. 1 is very very limiting. I had a card today that needed 2 such fields to calculate differences in days between 2 sets of 2 dates and I could not complete the task. The alternative is to create 2 formula fields on the object which seems silly for just 1 report that one user or small group uses in a large Org