Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.
Knowledge Base
How can I create a log to track changes made to a text field like [Status]?
Many customers want to log or track changes made to a field. There is a simple way to do this using Dynamic Form Rules. In this example we'll build a text field to track who made changes to a [Status] field, when they made the change, and the value they entered into the field.
In our example we want to track changes made to a Text Multiple Choice field called [Status]. Make sure this field is on a form and that users have permission to View/Modify the field in their role.
Create a new text field in the same table to contain a log of changes made to the [Status] field. Label this field [Status Change Log]. Edit the field properties for this text field and set the following text options:
+ Append Only: YES - Tight Style (Note: when changing this setting you'll be presented with a dialog window explaining that if you use append-only you cannot have autofills enabled. Click Ok to proceed.)
+ Prepend rather than append new text: checked (Optional. This places the most recent change at the top of the log.)
+ Use full names rather than screen names: checked (Optional. This makes it easier to identify the user who made the change.)
+ Include the time-of-day: checked (Optional.)
+ Data Entry: Type-In
Now create a Form Rule on the form that people use to edit the records in this table. There are a number of ways to get to the Form Builder screen for a form, but an easy way is to Edit a record in the table and click the "Customize this form" icon in the upper right of the page. When asked, click "Edit the Rules for this form in the Form Builder"
Click the Add New Rule button.
Set a condition: WHEN "the record is saved"
Click 'Add Condition'
Set a condition: and 'all' of the following conditions are true: 'Status' 'has been changed'
Set an Action: Change
Select the field to change: [Status Change Log]
Select the value to change it to: The value in the field... [Status]
Uncheck the option: "change" actions only fire when conditions become true
SAVE the form
Now, when you change the [Status] in a record, the [Status Change Log] will record the status change and capture who made the change and the time/date of the change. You can use either field when building reports.
* OPTIONAL: As an added protection you can make this change log field "Read Only" so that users cannot inadvertently add a value to this field manually from the form. To do this, click the ELEMENTS tab in the form builder. Highlight the form element that represents your [Stats Change Log] field and in the right panel of the form builder check the option to make the field "Read Only - even when used for data entry.
* NOTE: Form Rules ONLY function when edits are made using this form. Grid Edit and other multi-record edit functions will not trigger this rule.
* NOTE: Read Only only functions on this form, so using Grid Edit makes it possible to add another entry to the log manually.
Derived fields (formula, summary, and look up fields) are now available to use in form rules! Please read the following help topic for more information : https://www.quickbase.com/help/form_rules.html
If you’re not familiar with derived fields, the following links explain the three types.
Look up fields : https://www.quickbase.com/help/create_lookup_field.html
Summary fields : https://www.quickbase.com/help/create_summary_field.html
Formula fields : https://www.quickbase.com/help/using_formulas_in_quickbase.html
- 42461 reads
Rate This
Similar Articles
Browse by Category
Knowledge Base Categories
- Accounts (35)
- Application (45)
- E-Mail (7)
- Fields (41)
- Forms (20)
- Formulas (18)
- General (68)
- Other Product (7)
- Pages (1)
- Product (5)
- Reports (15)
- Roles (4)
- Search (1)
- Tables (6)



Comments
I tried this, but the problem
I tried this, but the problem I ran into is that it doesn't always work.
I have about 15 fields that I need to track changes to.... and it only works some of the time. The problem I'm running into is that I can't determine what causes it to trigger and what doesn't.
Any ideas?
Post new comment