Tweet
FYI using espcloud - cannot use a code/backend suggestion :)
I was trying to do this by using the "condition for this field to be read only" option.
Here is the problem.
For the regular user, it works fine.
For the Portal user, it doesn't have any effect
Question: do formulas only apply to regulars users on a given form and not users logging in via the portal accessing the same form?
The Use Case is the client wants to prevent a Portal user updating the Mentor (text) field if someone has already updated it. I was handling this by hiding the Status field from the Portal user. The regular user would change the Status at will, either editable or read only based on what they want to do.
But the condition doesn't seem to carry over to the Portal User view of the same form. In this case the Meeting Detail view.
I was trying to do this by using the "condition for this field to be read only" option.
Here is the problem.
For the regular user, it works fine.
For the Portal user, it doesn't have any effect
Question: do formulas only apply to regulars users on a given form and not users logging in via the portal accessing the same form?
The Use Case is the client wants to prevent a Portal user updating the Mentor (text) field if someone has already updated it. I was handling this by hiding the Status field from the Portal user. The regular user would change the Status at will, either editable or read only based on what they want to do.
But the condition doesn't seem to carry over to the Portal User view of the same form. In this case the Meeting Detail view.
Comment