Field locking

[panchristo]

What is considered the best practice for locking a specific field on every record after being edited once? (But also have a NotEmpty AND Unique validation option)

In other words, I have a field which needs to be filled in every record, be unique and once validated not being accessible.

I suspect that setting another field to 1/0 by a script is a potential vulnerability if someone can access it, isn't it?

I was thinking of employing a OnRecordCommit script trigger to prevent commiting before editing once, and then comparing creation and modification timestamps.

What do you think?

I still think however, that if one gets access to the fields from another layout he could bypass it. Any ideas?

[bcooney]

You'll need a record access rule that allows editing if the field is empty. I'd also provide a dialog before the commit, just in case the user wants to edit before being locked out. Often I give an admin priv set access to "unlock" the field/record.

[panchristo]

The solution is always simpler than I am thinking of. Great idea, thanks a lot bcooney,

I'll put it in rightaway.

:thanks:

[Squeaky Data]

Would the record access if not empty lock out the ability to edit the entire record rather than just the single field?

[panchristo]

:thumbup: I think you're right.

Any ideas?