Forum Discussion
_anomDiebolt_
11 years agoQrew Elite
> ...more changes then more longer field.
But this is the natural result of logging all the changes - it is going to take up more space if there are numerous changes. Beyond the general idea of using script to log changes to fields, you could track just the last n changes or perhaps just the changes made during the last 30 days. And where you store the changes is another dimension you can explore.
Also I should mention that the code I provided works for simple text and numeric fields. If you start logging checkboxes or lookup fields additional logic is needed. Date fields create another complexity. Date fields changed by direct user input trigger a change event but dates entered through the popup calendar are made through JavaScript an do not generate a change event (you have to use periodic polling to detect date changes). These issues have come up (and have been solved) with some clients exploring other logging scenarios. This is the type of solution which will evolve as users try it out.
But this is the natural result of logging all the changes - it is going to take up more space if there are numerous changes. Beyond the general idea of using script to log changes to fields, you could track just the last n changes or perhaps just the changes made during the last 30 days. And where you store the changes is another dimension you can explore.
Also I should mention that the code I provided works for simple text and numeric fields. If you start logging checkboxes or lookup fields additional logic is needed. Date fields create another complexity. Date fields changed by direct user input trigger a change event but dates entered through the popup calendar are made through JavaScript an do not generate a change event (you have to use periodic polling to detect date changes). These issues have come up (and have been solved) with some clients exploring other logging scenarios. This is the type of solution which will evolve as users try it out.