+9Hi Community,
I need to make this field read only for every users in the environment.
I tried to make it read only by RMB on the page >Properties > Read only
but it reflected for only the current account. When I logged in to other user accounts, I can still edit the field.
Please help how to get this done..
thanks in advance.
Regards/
Hari
Best answer by Thushitha Chandrasiri
Hi
As Stephen mentioned, you can make the field read-only in the required base profiles, so that the users attached to that base profile will have that field read-only. It is useful to make the field read-only to particular set of users.
If you want the field to make read-only for all the users (even for app owner), you can do that defining it as a conditional field as below.
For an example, if you want to make the Receipt Date in PO header read-only, you can do it as below.
Thanks,
+11You store this behaviour against a Base Profile and roll this out to all the end users.
+21Hi
As Stephen mentioned, you can make the field read-only in the required base profiles, so that the users attached to that base profile will have that field read-only. It is useful to make the field read-only to particular set of users.
If you want the field to make read-only for all the users (even for app owner), you can do that defining it as a conditional field as below.
For an example, if you want to make the Receipt Date in PO header read-only, you can do it as below.
Thanks,
+19You could make a custom event that compares the old and new values and throws an error if they disagree. This ensures every means of updating the field is blocked. This also gives you the ability to define logical exceptions.
+9Hi
As Stephen mentioned, you can make the field read-only in the required base profiles, so that the users attached to that base profile will have that field read-only. It is useful to make the field read-only to particular set of users.
If you want the field to make read-only for all the users (even for app owner), you can do that defining it as a conditional field as below.
For an example, if you want to make the Receipt Date in PO header read-only, you can do it as below.
Thanks,
Outstanding, This is a complete new information to me. Thanks a lot
+9You could make a custom event that compares the old and new values and throws an error if they disagree. This ensures every means of updating the field is blocked. This also gives you the ability to define logical exceptions.
Thanks a lot
+9You store this behaviour against a Base Profile and roll this out to all the end users.
Thanks a lot
+21Hi
As Stephen mentioned, you can make the field read-only in the required base profiles, so that the users attached to that base profile will have that field read-only. It is useful to make the field read-only to particular set of users.
If you want the field to make read-only for all the users (even for app owner), you can do that defining it as a conditional field as below.
For an example, if you want to make the Receipt Date in PO header read-only, you can do it as below.
Thanks,
Outstanding, This is a complete new information to me. Thanks a lot
You are most welcome ! 😊
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.