Discussions

 View Only

  • 1.  Locking a Field Once populated

    Posted 10-07-2016 04:09

    I have a project completion date which is initially populated by PMs. But once entered, I want them to seek an approval to change it.  I have a process in place for this so that such requests are approved and the new date becomes 'approved completion date', a separate field. 

    I would like to enforce the discipline. Tried to look at dynamic form functionality.  The most I can do is to link to current date.  But that still does not work. How to ensure that date is filled once and then becomes read only.   

     



  • 2.  RE: Locking a Field Once populated

    Posted 10-07-2016 11:53
    Set up a field called [Record ID# mirror]
    With a formula of simply [Record ID#]

    (  for some reason, form rules do not let you use the record ID field directly. )

    Then make a dynamic form rule

    When  multiple conditions are true

    When [Record ID# mirror] not equals (blank)
    Users is not in the Role High Level

    Make read only [Project Completion Date]

     In other words, what is happening here is that before the record is initially saved, the record ID does not exist so it is blank. Under those conditions you were OK to let anybody enter a project completion date. But once the record has been initially saved once and a record ID number has been assigned then the normal lower level role permission users are not allowed to edit that field.


  • 3.  RE: Locking a Field Once populated

    Posted 02-14-2017 21:42
    This is really clever - will begin testing it this week. Thanks for the contribution.
    Gerry


  • 4.  RE: Locking a Field Once populated

    Posted 10-08-2016 01:21
    Many thanks Mark.  I used this solution of yours in relation to another issue,.  So I have a field in place.  Great innovation.


  • 5.  RE: Locking a Field Once populated

    Posted 08-16-2017 22:50
    Mark, in case where record was saved, however, the field in question was left blank or the info was not available at that time and the field is now read only using this solution. How could I ensure that user is able to edit one time using this solution as long as the field is blank?  


  • 6.  RE: Locking a Field Once populated

    Posted 08-17-2017 01:24
    No problem,
    change the form rule

    when multiple conditions are true
    when ALL of the following are true

    Date is not equal to (leave blank)
    [Record Id# mirror] is not Equal to blank

    Make read only [Project Completion Date] 


  • 7.  RE: Locking a Field Once populated

    Posted 07-30-2021 10:30

    Hi! I realize this feed is several years old, but it's very useful to me now :)

    Does this ensure that when a bulk upload is performed, the fields that are marked read-only will not update? Or does this only work when editing a record in form mode?

    I'm trying to lock certain fields from being edited in form mode, but also from being updated during a bulk upload/update.

    ~Renee



    ------------------------------
    Renee Hansen
    ------------------------------

    Original Message


  • 8.  RE: Locking a Field Once populated

    Posted 07-30-2021 10:32
    Dynamic form rules will only work when a person is editing a record in the browser on a form. They will not prevent fields from being updated when doing a bulk upload.

    I think you should post this as a new question describing your full situation and then the community can see if we can offer any suggested solutions.

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------

    Original Message


  • 9.  RE: Locking a Field Once populated

    Posted 08-17-2017 01:41
    very kind of you for your help.  This worked well.