Skip to main content
Question

Change user in field who modified another field

  • June 25, 2019
  • 0 replies
  • 55 views
I have a field called "Anticipated Purchase Date", which is a date field.  When the date is entered, it will automatically update the field "Anticipated Purchase Date Entered by" (which is a user field and read only).  I created a rule for this to happen. See pic.

the issue is that if someone decides to select a new date for "anticipated Purchase date" after the initial entry of a date, then the field "Anticipated purchase date entered by" will not update.  It will be keep the initial user in there.  How do i make it that when the "anticipated purchase date" is modified by a new user, the "purchase entered by" field changes to that user?  Based on what i did, it will only change if i delete out the "Purchase date" and enter the date again, then the "Anticipated Purchase Date entered by" will change to the new user (because that is how the rule is set up).  Thank you.


    This topic has been closed for replies.

    Instead of using a form rule from your screenshot - you can use an automation to populate it for each modification to the record where that specific field was changed. In the automation - you would write the value of 'Last Modified By' - the person who last updated the record - and copy that into the 'Anticipated Purchase Entered By'


    Chayce Duncan | Director of Strategic Solutions
    (720) 739-1406 | chayceduncan@quandarycg.com
    Quandary Knowledge Base
    • ShaneSelasky
    • Author
    • Registered
    • June 26, 2019
    working with automation, it seems this is more for many records to change.  I just want the one field to change when another field is modified for the one record.  Is this possible with automation?
    When you are setting up the action - there is an option to 'Filter'. 

    In that filter - set it so that you are editing where Record ID# = The Record ID# of the record that triggered the automation originally.


    Chayce Duncan | Director of Strategic Solutions
    (720) 739-1406 | chayceduncan@quandarycg.com
    Quandary Knowledge Base
    • TomMusto
    • Registered
    • June 27, 2019
    I think an automation is overkill for this. Here's how I would do it:
    • Create a new field named Anticipated Purchase Date Compare (match the field type to whatever Anticipated Purchase Date is)
    • Create a form rule that says: When Anticipated Purchase Date is not equal to the value in Anticipated Purchase Date Compare Action change Anticipated Purchase Date Changed By to the current user
    • Create a form rule that says: When the record is saved and Anticipated Purchase Date Compare is not equal to the value in Anticipated Purchase Date Action change Anticipated Purchase Date Compare to the value in Anticipated Purchase Date
    This will maintain a copy of the Anticipated Purchase Date from the last time the record was saved in a different field and whenever these two fields show different values, the first form rule will change the User field to denote who made the most recent change. The second form rule will then re-sync the two fields after the User field has been changed and the record saved. This prevents someone that is editing other fields in the record (but not touching Anticipated Purchase Date) from being noted as the person that changed the date fields. Hope this helps.

    -Tom
    -Tom
    Terms & ConditionsAccessibility statement