Hi Joseph, A couple further comments.... Related to Issue 1 above, yes, the new calculation engine will have optimizations for nested calculations to work out and better handle those scenarios. Relate to Issue 2, you normally do not need to use the [Group.Header] syntax in Professional model calculations. Sometimes you do, such as if referencing parent fields outside the group where the calculation is performed. But if you're only referencing headers within that Group, you can just reference headers by header name, which should save you some characters. Such as: Also, upper(), lower() etc. functions are high on the priority list for new functions - to avoid workarounds like the nested replace() function example above. (Not sure why your post was flagged as abusive - I still see both above.)
↧
