ACR Rules

  1. Home
  2. Docs
  3. ACR Rules
  4. Performance (29)
  5. Entity should have a maximum of N calculated attributes

Entity should have a maximum of N calculated attributes

Calculated attributes are continuously re-calculated upon request of the entity and often a cause of bad performance. Instead, it is recommended to pre-calculate values in before-commit microflows or find a way to do the calculation on the client-side. See this post for more information https://forum.mendixcloud.com/link/questions/85957

It is possible to set this rule to allow a maximum of 0 calculated attributes to completely prohibit calculated attributes are not allowed at all.
Alternatively, it is possible to configure a small number of allowed calculated attributes per entity e.g 1 or 2.

Noncompliant example: