How to work around LeanIX limitations regarding calculated fields updates ? 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.IssueLeanIX 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 rig