Locking a Field Once populated
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 app...
Forum Discussion
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.
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.
- This is really clever - will begin testing it this week. Thanks for the contribution.
Gerry
