Skip to main content

Nested Calculated Fields

While some systems limit the calculated fields to be dependent only on fields from the underlying sources or support dependency among calculated fields as long as they are named with a certain order, SQL Frames supports defining nested calculated fields without following any naming conventions. This is becuase SQL Frames compiles all the fields, establishes the dependency graph and then computes them in the right order. This makes them very convinient and powerful to end users and coupled with UDF with Excel-formula like syntax, they can be used easily by citizen developers.


Below is an example of 3 calculated fields with second field depending on the first while the third dependent on both first and second. In addition, they are also defined in reverse order (just for illustration, typically users would likely define them in the right order).