Which element cannot be used to create calculated attributes in an aggregate?

Calculated attributes in an aggregate are designed to derive values based on existing data from the source entities or through functions that can be utilized in SQL. When creating these attributes, you can work with the raw values from your entity attributes, apply built-in functions, or use variables.

Utilizing the value of the attributes of the source entities allows for straightforward calculations derived directly from the data structure. Similarly, built-in functions can operate on these attribute values to perform calculations like determining string length or performing arithmetic operations.

However, server actions are distinct in that they encapsulate more complex procedural logic, including external processing or manipulations that extend beyond simple attribute calculations. Server actions can’t be directly integrated into the calculation context of an aggregate in the same way that attributes, functions, and variables can. This limitation comes from the nature of server actions, which involve executing code rather than returning static values that can be directly computed in the context of an aggregate. Thus, they cannot be used to create calculated attributes in an aggregate.