In a web application, I have a form with hundreds of computed fields. I planned on having a single form button handle the calculations of all these fields. Even though @Commands evaluate top to bottom, can the button formula somehow calculate the value of any computed field which refers to values of other computed fields that are both above and below it on the form? Might there a better design option than a form button formula for this scenario?
Thanks.
Subject: RE: Order of Evaluation for Computed Fields
What exactly are you trying to accomplish? It’s hard to evaluate a design in the absence of any requirements. Not that you’ve really described the design either…
If you’re asking, can your button formula point to a certain field and tell that field to recalculate itself, without calculating all the other fields, then no, there’s not a way to do that except to duplicate the field formula as part of your button formula and just assign the field.
There’s an @Command to refresh all the fields, but in a web application, I don’t think you’ll be able to use the @Command and then resume execution of your formula to retrieve the values resulting from your calculation.