This post outlines how to store basic record history / changelog (for front-end access) in a single text field, but using a new approach.
Other methods I’ve seen involve creating a new database table for storing the changelog, and adding 1 connected record per change via record rules or custom code (eg via Knack Toolkit Library).
These work well but have a major disadvantage of using a large amount of your (limited supply of) database records just to store the history. Furthermore, the code-based methods require use of custom code, which some are not comfortable with.
My method uses 100% native features and also avoids the need for using one database record per changelog/history. Instead, the changelog is stored in a text field on the record you’re interested in storing history for.
The basic method outlined below could also be extended to include more data eg who made the change, what the value changed to etc. However, it may become a bit cumbersome to set up and use if you need a lot of detail stored about each change.
Here is the method. Let me know if you try it and post any questions below!
