Efficiently use pipelines for record change logs

Question

Hi,I was going through the quickbase university courses and came across this use case of using pipelines' Quickbase Records Updated feature to log changes to a table. Building Powerful Pipelines Using included FeaturesI have a similar use case, but I have nearly 40 fields in the table and I only want the log a single changed field in the log table. In coding, I would do something like:

for field in table_fields:
    if field.prev.value != field.current.value:
        create_logs_record(field.name, field.prev.value, field.current.value, ...)​
Is there a way I can efficiently do this in pipelines using jinja or some other method?Currently, I have a trigger on update and then a long series of `if changed, create record else ...` which is tedious to create and would be difficult to modify.------------------------------Bradley------------------------------

MarkShnierYou · Accepted Answer

One solution is to log every field in 40 Steps. That will take two pipelines.

Then each night run a step to purge records where old value and new value are the same.

Filter off from any reports where the old and new values are the same and your users will never know that a day's worth of record where there was, for the most part, no change

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

Sign up

Login to the community