I am migrating the Travels project from 2023.06-ext11 to 2024.06-ext5. I got a computation called MealAllowanceReductionSingleDayHelpCalculation, and it uses the field MealAllowanceFullDayValueHelpField for calculation. In the form model, MealAllowanceFullDayValueHelpField depends on another enumeration field, and in most cases, it is set to “Hide”. After migrating, the dependencies are set to “Not relevant”, and I got the error “error text for computation of MealAllowanceReductionSingleDayHelpCalculation” when running full validation.
I already know I got the validation error because MealAllowanceFullDayValueHelpField is “Not relevant” and the computation cannot use it at that moment. But we have many cases like this in our project, and the fields depend on each other, even more complex than this example.
Do you have any suggestions on how to best handle this case? I attached some images to explain it clearly.
Thank you.
from what I know about these models, you mix two different business requirements with one Helper Field:
“A value contributes to the final allowance”
“I am not interested in the individual numbers, just show me the final allowance” = “Hide Calcs”
I would separate out the last part and use a Dependent Control for this. Here you can conveniently set a whole Control Grid (with all you helper fields) to hide/show in one go.
For the remaining part: If I select “Show Calcs” I would expect, that I see all the Fields, that contribute to my final allowance. Why are there Fields, that contribute to the final sum but are not shown? Is that confusing for the user, if they select “Show me all the contributing Fields” but the number just don’t add up?
→ Why would you hide a Field sometimes (even if Show Calcs is selected) that contributes to the final sum?
Hi @felix-blazing-river,
Sorry for the late response. We have just completed our upgrade, and I wanted to update you on our decision. To summarize, our discussion ended with two possible solutions:
- Solution 1: Keep the field dependency as it is and update the computation logic to cover all cases.
- Solution 2: Remove the field dependency, group all the fields that have the same show/hide condition in a control grid, and apply the group dependency instead.
With solution 1, the computation logic would become more complex and harder to maintain. Based on your and Ben’s suggestions, we decided to go with solution 2. The disadvantage of solution 2 is that if a field has more than one dependency condition, we must have more than one control grid, but we can accept that.
Thanks a lot for your support!