Qrew LegendJust adding two more comments on this. The first is that an alternative is simply logging the old value and the new value any time any of the field to your tracking changes. This will result in many records, which have no change and you were just purchased them out overnight.
Just adding two more comments on this. The first is that an alternative is simply logging the old value and the new value any time any of the field to your tracking changes. This will result in many records, which have no change and you can just purge them out overnight. You would have an embedded report on the table to show the change log, but you would have a filter on that report to not show records where there was no change in the field
The other tip is to include the table name in your logging table, and that way you can use the same table to log changes in many different tables and with the report link field, it would only include logging for say customers on the customers table and parking for orders on the orders table.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
Qrew LegendI think you will find it problematic to construct your Pipeline branching, so that's why I suggest logging the old and new value for each field you are tracking, knowing that the vast majority of those log records will end up getting purged overnight as there is no change in that particular field.
