Script to update calculated fields

If you look at the List View, there is an option for "Recalculate Values".

That is part of the massupdate actions and the corresponding code can be found in 

clients/base/views/massupdate/massupdate.js

The action executes the 

updateCalcFields: function 

which as you can see from the code is just a mass save:

    /**
     * Called to allow admins to resave records and update thier calculated fields.
     */
    updateCalcFields: function() {
        this.hideAll();
        this.save(true);
    },

In other words, to trigger a calculated field to update all you need to do is save the record.

The down side is all your Modified by and Modified Dates will change on every one of those records, which is not necessarily something one would want to do when modified date is important for reporting purposes.

But it is the cleanest and safest way to do this.

FrancescaS

Thanks Francesca Shiekh
Indeed I forgot and should have mentioned the desire is to not change the modified by or date.

I remember somebody on the old community mentioning this was possible and shared insights for the method and maybe even the script (was it Blake?) but can't find it.

Have a customer with more than 300k of records in one module, so ideally this script could then be run in background or only run overnight on a scheduler.

Ideally the Sugar product team could look into adding this much needed feature for the greater good?

Come to think of it, back in v6.x it was possible to set 

   $bean->update_date_modified = false;

   $bean->update_modified_by = false;

before saving the bean to preserve the modified by and modified date.

I think that still works. You would need to test it.

In that case you could add a checkbox to track which records were reprocessed.

Then write a nightly scheduler to retrieve the beans for each of the non processed records via SugarQuery (excluding those where your checkbox tracking field is set).
For each bean found set those two variables above to keep the modified date/modified by from being modified and set the tracking checkbox, then save.
The save action would perform the calculation, the checkbox would track that you processed that record so you can excluded from the rest round in your SugarQuery.

Once you are done reprocessing them all, you can remove the checkbox field.

The other option is as Jeroen Somhorst suggested, instead of using the bean, reproduce the formula's calculations in code and save the results using a SQL statement which does not trigger any additional logic.

Francesca

Come to think of it, back in v6.x it was possible to set 

   $bean->update_date_modified = false;

   $bean->update_modified_by = false;

before saving the bean to preserve the modified by and modified date.

I think that still works. You would need to test it.

In that case you could add a checkbox to track which records were reprocessed.

Then write a nightly scheduler to retrieve the beans for each of the non processed records via SugarQuery (excluding those where your checkbox tracking field is set).
For each bean found set those two variables above to keep the modified date/modified by from being modified and set the tracking checkbox, then save.
The save action would perform the calculation, the checkbox would track that you processed that record so you can excluded from the rest round in your SugarQuery.

Once you are done reprocessing them all, you can remove the checkbox field.

The other option is as Jeroen Somhorst suggested, instead of using the bean, reproduce the formula's calculations in code and save the results using a SQL statement which does not trigger any additional logic.

Francesca