Skip to main content

The advance formulas, using case statements, are great, when they can be used, e.g. 

 

Formula for working out GRR of an opportunity.

 

This reduces the need for me to have a rule which runs regularly in order to calculate, and provides real-time data. 

However there are limits on both which fields types can have an advanced formula, and which field types can be used in one. If all field types were available we could remove many MANY rules.

A few examples:

I want to set a boolean as true or false based on a date field. E.g. case when LastUpdated > today()-7 then True, else False.

I want to set a segment (picklist) based on ARR E.g. case when ARR is null then null, when ARR < 10000 then Small, when ARR < 50000 then Medium, else Large

Thanks,

Absolutely right. I couldn't agree more.

The most critical constraint is that Fx fields are both limited to certain data formats and require the input data type to match the output data type. This severely restricts our ability to build flexible, transforming logic.

When complex logic can't be contained in a single rule (e.g., needing to add another dataset), we're forced to create subsequent, chained rules. This necessary workaround introduces a high risk of a data mismatch due to timing discrepancies between the fields' execution.

Terms & ConditionsCookie settingsAccessibility statement