Hi guys,
I want to have a field โCommentsโ always visible because it may already has data, but make it Editable only if the user email logged is = โtest.mail@gmail.comโ
I already tried with Editable_if expression, but what happened is that if I am not the user with that email, the field is not shown to me. And I already tried in the Show_if expression = True() it appear even if field is blank but only in View, not when not work when Edit the form.
Solved! Go to Solution.
We donโt show empty non-editable fields because forms sometimes can have many of these and they do not show meaningful information.
If the issue is that the โFecha Compromisoโ field might be required when the Status field is set, but the current user cannot fill it in, you can define a Valid_If constraint on the Status field to indicate this.
I hope I am correctly interpreting your requirements.
Editable_if: USEREMAIL() = โtest.mail@gmail.com" should be what you want.
The field should always show in a form view if Show is on (no expression).
If youโre wanting it to show in a detail view even when blank, I think you can set it as a Quick Edit column.
Actually I already tried when the Show is on but same problem in the edit Form mode.
Youโre saying that with the conditions:
that the Comment field is not visible in the Form view?
Letโs see some screenshots of the app and the column definitions.
Exactly
I just saw that the issue is only when the field is empty, if there is nothing, the field is not shown. I will show the case with the real field, called โFecha Compromisoโ
here when the user logged is โtest.mail@gmail.comโ, the field is editable (good):
Here when it is other user, the field is Not editable (good):
and this is the error, when itโs another user and the field is empty, โFecha Compromisoโ is not shown:
And my case is that, the field โFecha Compromisoโ becomes required if a โStatusโ field is set to โIn Processโ, but the same field must be filled only by the user โtest.mail@gmail.comโ
We donโt show empty non-editable fields because forms sometimes can have many of these and they do not show meaningful information.
If the issue is that the โFecha Compromisoโ field might be required when the Status field is set, but the current user cannot fill it in, you can define a Valid_If constraint on the Status field to indicate this.
I hope I am correctly interpreting your requirements.
Thanks Praveen, and I just saw in other post the same you said. I changed a little bit the logic in my App to get almost the same, so I am fine for now.
Would be fine that team updates the helping article with what you said:
It seems to me that behavior should be revisited as there are already ways to control which field are shown / relevant, e.g. list of columns in the form and Show checkbox / formula.
for some forms, it would be relevant to be able to display some information relative to the context for the user - e.g. bug ID, bug title before they update the priority, add a comment, update the status...
User | Count |
---|---|
43 | |
32 | |
25 | |
23 | |
14 |