Skip to main content
Question

How to work around LeanIX limitations regarding calculated fields updates ?

  • January 14, 2026
  • 1 reply
  • 22 views
J

Hello LeanIX Community, 

I’m working on a setup where I need to use parent/child relationships inside Application Fact Sheets to run some calculations and to control the visibility of other fields based on whether a parent exists.

I think I’ve hit a fundamental limitation in LeanIX and I’m looking for advice or best practices to handle it.

Bit of context 

I have Calculated Fields that depend on whether a Fact Sheet has a parent. I also need to show or hide certain fields based on this logic. So basically the UI depends on the calculated value, and the calculated value depends on the presence of a relation.

Issue

LeanIX does not evaluate calculated fields:

  • when a Fact Sheet is first created,
  • when the page is opened,
  • or immediately after adding/removing a relation.

They only update after a browser refresh. This creates two problems:

  • At creation time, calculated fields are always Blank, even if the logic should return “No parent”.
  • After adding a parent relation, calculated fields do not update right away — they only update once the user refreshes the page.

I assume Conditional Attributes cannot rely on a calculated field at the moment the FS is opened or when a relation changes.

Identified Impacts 

  • The UI cannot correctly show/hide fields on the first load.
  • Adding or removing a parent does not immediately update the calculated field.
  • Conditional Attributes based on a calculated field do not react until SAVE.
  • It becomes impossible to drive UI logic based on parent/child status without user intervention. (?)

My questions for you

  • Is there any supported way to get a calculated value for “has parent / has no parent” before the first save?
  • Is there any method to trigger a recalculation of a calculated field immediately after a relation change?
  • Is there a recommended pattern to control UI visibility based on relations, without waiting for SAVE or REFRESH?
  • Can Automations or the API be used to work around these delays, or are they subject to the same UI limitations?

I’m looking for general best practices for anyone who needs to build logic based on parent/child relations and needs the UI to reflect that state accurately.

Thanks a lot in advance!

 

1 reply

Thomas Schreiner
Forum|alt.badge.img+3

Hi ​@Julien_Blanc, the execution time for calculations is usually not an issue, since every calculation depends on certain input fields that are referenced in its code and is recalculated “immediately” (or rather: soon) after one of the dependencies is updated.

The issue that you are mentioning is the UI refresh topic. Even if an automation or calculation is executed immediately, it will only show when the UI is refreshed (in most cases). For some topics like simple calculations, this has been solved already by visually showing the ongoing recalculation (grey out the field, then populate the new value), but this is still an ongoing process.

Since LeanIX is currently investing heavily into the technical basis of automations and calculations, I personally expect some improvement in the next 6-12 months.

    Terms & ConditionsCookie settingsAccessibility statement