Timeline for What is the best workaround for the 20 field history tracking cap?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 1, 2018 at 12:57 | comment | added | sunny | I like the idea of using JSON but it won't store historical field history, only the most recent version. I think this proposed solution is most useful for creating an undo function | |
| Jan 5, 2017 at 16:16 | comment | added | Scott Pelak | Correct, that's the catch to using JSON to store data. | |
| Jan 5, 2017 at 10:05 | comment | added | Andy Hitchings | I really like the idea :) But one wouldn't be able to run standard reports on this then since it's a single long text area field? | |
| Oct 11, 2016 at 23:31 | history | answered | Scott Pelak | CC BY-SA 3.0 |