I decided to spend some time with the new FormulaEval beta in Summer '24 and while it seems mostly solid, I think it would add a lot of value if it had options you could not normally support in Formula fields.
For example, providing support for maps, or primitives like the Object Class would allow much more powerful options, because it would let you aggregate data into a single object under whatever property name, and then build formulas off of that.
Hi Cody,
Thanks for the feedback.
With the Map support, do you see the formula instance being provided a Map as input and then pulling any values out based on the Map keys?
This would present some challenges with the current builder approach where we perform validation that the related object has the required fields/properties for the formula to reference. Referencing a map would need to be more dynamic with runtime validation.
Can you provide an example where you would use this functionality. Having a use case would be helpful in validating possible solutions we could come up with.
