Skip to main content
Question

History of Changes

  • December 26, 2017
  • 0 replies
  • 76 views
I am working on building a new CRM and Project management application for my company. I am pretty far along but one of the features of our old system that everyone liked and we are trying to keep is the ability to track changes to records. In our current system, there is an automated "notes" section that gets updated whenever there is a change and it lists what user did what change. I was wondering if there was a way to get this functionality in Quickbase. I have attached a screen shot of what it looks like:
    This topic has been closed for replies.

    • anomDiebolt
    • Registered
    • December 26, 2017
    With script it is possible to use a Text Append/Prepend Logging field to keep track of changes to other fields. Normally a logging field keeps track of changes to text input into the logging field. However, with script you can prevent human input into the logging field and instead arrange for other fields that are that are modified to be formatted and automatically inserted into the logging field.

    There is actually a demo I created of this that if you are interested I will attempt to locate.

    Found it here:

    https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=305
    Justin,
    You can do history logging natively without script.

    If there are less than 10 fields to track, I suggest making an Action to Record the changes.

    The technique is to make a Table called Change history with the fields

    Related Parent
    Field name
    Old value
    New value
    Changed by

    Make a relationship to the table you are trying to track

    Setting up an Action is similar to setting up an email Notification.

    Make an Action to Record when a certain field changes to write out a history log record. There is a limit of 10 Actions per Table.

    Give it a try to get t(e first one done and post back if you have questions. Once you have the first Action done, you can copy i5 t9 make the 2nd one.
    Terms & ConditionsAccessibility statement