Using script you can stuff
anything you want into a multi-line text field in essence defining your own field type. So the only question is what format do you want to record your "history of changes" information in? Provide an example of some date changes.and describe the series of changes that were made.
Here I create a handy dandy
chessboard field where the position of all the chessmen are stored as
JSON in a multi-line text field.
https://haversineconsulting.quickbase.com/db/bmpbjbbxx?a=er&rid=2You can also use a file attachment field to represent your custom field type. Normally the only thing you can do with a file attachment field is upload or download the file from / to your computer. However with script you can read and write a file (or create a file from scratch) to represent the state of your custom filed.
When a form opens you
(1) read the file attachment field,
(2) make the necessary modifications to the form to make the custom field viewable / editable to your human user in a convenient manner and
(3) repackage the file attachment when the form closes if your custom field has been modified.
The rules have changed - everything is possible with QuickBase technology. Actually the rules haven't changed - this feature is used extensively in other quadrants where QuickBase technology has terraformed more rapidly than on this planet.