taubes
Member
Hi,
A little inconsistency. If you have a calculated field referencing a cascade parent and filter field:
If you update the cascade parent the calculated field is not properly updated. It correctly shows the new cascade parent but incorrectly the old non-matching cascade filter value although no longer visible in the browser.
When you save the entry it then updates calculated field correctly again also when you change the cascade filter value. So not a big problem but annoying when you program the calculated field.
Best
St
A little inconsistency. If you have a calculated field referencing a cascade parent and filter field:
If you update the cascade parent the calculated field is not properly updated. It correctly shows the new cascade parent but incorrectly the old non-matching cascade filter value although no longer visible in the browser.
When you save the entry it then updates calculated field correctly again also when you change the cascade filter value. So not a big problem but annoying when you program the calculated field.
Best
St