Is it possible to log edits within a date field?

Well one thing that you could try to set up a field called date log  which is a another text field set to log changes. And then using form rules set up a rule that says when the record is saved and the date field has changed change the date lock to the value in the field Date.

 But because this is based on form rules, that means it will not work in grid edit.

We are moving more to custom forms, so that should not be too much of an issues.
Sounds promising.
Would the text log field, update with a user and date per normal?
Having an additional field would allow filter in certain reports to just see the current, so that is also beneficial.
Can you please advise what the fom rule would look like?

The form rule would look like

When the record is SAVED
and the [Date field] has changed

Action

Chage the value of the field [[my text field set to log chnages] to the value in the field [Date field]

And yes, a field set to log chnages, does always record who did the update and the date and optionally the time of day.

Mark, does this mean that logging is inly available on text fields? 

A more sure fire way to log data changes is through a Data Change table.  Then you just have a button to change the date.

You also wont have to maintain a bunch of different forms with their form rules.

By creating a date change record, you automatically keep track of who, and when.  You can add a bonus feature really easy as to the why.

Long term this is the most efficient and cleanest way to track your date changes.

I can explain in more detail how to set this up properly if needed.

Thanks.  I am already using QB Actions.  Is this what you are referring to? 

Hello Matthew,
 
out of what you wrote above I am not able to reapply it. Could you please send me a more detailed description of how to set this up please.

Just one Field;
"Date"
A second field would be needed if you had a "Why"
>
Each 'Project' can have many date changes.
>
Summarize Max Record ID
>
Pass new max RID as lookup
>
Summarize Date where max RID = Record ID#
Now you have your log of date changes with time stamps and record owner.

Thanks a lot,
Christina

Christine,

Matthew is suggesting that you create a child table of dates and make your date updates there.  Then you will have a very clean audit trail of the date changes.

Post back if you need help with that.

Thanks to QuickBase webhooks it's now pretty easy to create history tables where you can log old record values.  Let's say you have a helpdesk Ticket table, you can create a TicketHistory table and use webhooks to create a new record whenever a Ticket is modified

Good point,  it now that we have ACTIONS we can set up a log table that way, and not need to struggle though the Webhooks Syntax.  So using that method, you just update the date normally and the ACTION will do the logging.

That's true.  Does actions handle bulk ops better than webhooks (like save on a grid edit)

That's true.  Does actions handle bulk ops better than webhooks (like save on a grid edit)

Yes they do handle Grid Edit.

Will check it out.  The way Web Hooks / Email Notifications handles bulk edits isn't ideal, would be pretty impressed if the action handles it differently.