I expect the value in the rollup field is being updated because you are forcing it to recalculate via the API using the Force Rollup Calculation from the Workflow Tools add-in. But you are looking at a record, which is a web page. There is nothing that happens in a workflow that will force the page to update in front of your eyes. You can test if this is what is happening by popping the record out to a new window, do some update, ass a payment line record for example, then check what value is in the database for the rollup field when the workflow has had chance to run (maybe in the original view, or an Advanced Find window). Options: Use JavaScript to do the calculation and update the value in a normal (not rollup) field. Use JavaScript to detect when you add a line to the sub-grid and force the screen to refresh (horrible). Use JavaScript to detect when you add a line to the sub-grid and refresh a web-resource on the form that displays the rollup value (slightly less horrible). Teach users to use F5 when they want to see the new value, maybe when they have added one line , or maybe after doing several before they need to see the total.
↧