Forum Discussion
1 person found this helpful
Right, so as you know, the reason they are called Dynamic Form Rules and not Dynamic Grid Edit Rules is because they only work on Forms.
So you have two choices, sort of low tech and hi tech.
Low tech is that you change the field type of that [Status] field to log changes and then have a new field that is a text formula field to parse out the ;latest status and the date of the change.
Here are the formuals for that.
Most recent value (formula text field type)
Trim(Right([my update field]),"]"))
Date of most recent update (this needs to be a formula date field)
ToDate(Left(Right([my update field],"["),9))
Who did the most recent update (formula text field type)
Trim(NotLeft(Left(Right([my update field],"["),"]"),9))
The other option is more technical and that involves setting up a Webhook to record that update date. YOu can read about Webhooks in the help docs, but realistically, unless you are really smart you will need some help getting your first one working. Then they become easier. :) I needed help and examples my first time.
Contact me via the information in my Profile if you want one on one assistance with webhooks or else go low tech.
Was this answer helpful?
Answered by:

QuickBaseCoach App Dev./Training , Mark Shnier, Principal
QuickBase Solution Provider 21 days ago
- ArchiveUser9 years agoQrew CaptainI use webhooks for this exact thing, and it works perfectly. Agreed that most people will probably need an example to set up their first one, but they are quick and easy once you know how to do them.
I hadn't thought of your "low tech" solution. Any thoughts on the pros and cons of using one solution over the other? Some cons of webhooks are that you get a limited number of them, and they change the "last modified by" field to whoever owns the webhook. Any downside to using the formula fields?