There are several strategies you could use:
- Using the "Log the edits to this field" feature in the Field Props and then, parsing the logged results (as Mark mentioned).
- Using Form Rules to listen for changes to a given field and setting a Date value elsewhere
- Using a Formula Field as a "proxy." Then, making the original field not reportable nor searchable. Instead, the proxy would be reportable and searchable. And by its nature, not "grid editable" (since its a Formula Field).
- Each QB table has a default "Date Modified" field (FID 2). You could uncheck the "Show the time" box on field Props and report on this value. But, I typically suggest leaving default behavior alone. So instead, I'll cast that value to dedicated presentation field via a Formula Field.
An example of the latter is creating a Formula Field not expected conversion "Type." So, we'd create a "Date" Field (not Date / Time) and name to "Date Modified To Date." Then, you'd cast the value via something like:
ToDate([Date Modified])
Often these "vanity" fields can get around limitations of only being able to display native field once on a given Form, simplify Pipelines and reduce visual noise on Reports by trimming the time portion off a Date / Time.
------------------------------
Brian Seymour
------------------------------
