Open jozef-budac opened 2 months ago
@jozef-budac can you please try it on production?
Discussed with @jozef-budac and seems to be gone
I can again observe the issue https://github.com/MerginMaps/mobile/assets/83582181/1237d2ed-544d-49d6-8ff7-43622a3c3b96
There is a problem with a scenario, when there is recursive apply on default update on multiple fields. I have one field with "apply on default update" and another one, which the same and is controlled by the previous field.
In the tc05_forms_derived, there is a tab
Data
. It is hidden till something is filled intoValue
on theInformation
tab. On theData
tab, there are 4 fields:Population
(sets population of bears in Slovakia)Limit
(sets limit, till somebody from Slovakia parliament is going to do about it)Danger
is the first field with "apply on default update" sets with value"Population" > "Limit"
Name
is the 2nd field, which is controlled by theDanger
field and has "apply on default update" set withif("Danger" IS 'false',' Bear safe',' Bear dangerous')
This means, that when
Population
is > thanLimit
, theDanger
should be true, andName
should beBear dangerous
. This is not happening and because of it, the Slovak parliament doesn't know what to do with it.In the video, you can see that the update of the
Name
field is delayed and with the next update has the correct value from the previous data update.Please note: if you are not familiar with conflicts between bears and politicians in Slovakia, you can freely ignore all the comments on this topic :)
https://github.com/MerginMaps/mobile/assets/83582181/988be761-900d-42f8-b920-0f11e39a2c4f