I have tried manually modifying it and it seems possible, but I am not sure if there are any unintended side effects.
My requirement is to have a logging summary table that rolls up the details of another fine grained logging table. However, it should be possible to disable generation of fine grained records, while still having the summary table maintain information.
I can guarantee that there will be no additions/removals to the child object when the rollup object is being updated.
I was just wondering whether there was some background process that periodically refreshes/updates the values, such that even if I were to enter something, the values would eventually get replaced? If anyone has done something like this before, please let me know.