locked
Issue with field security profile fields RRS feed

  • Question

  • Hi,

    I have a question concerning the field security profile fields. I created a custom field called TEST and I enabled the field security setting for this field.

    Next, I created a field security profile and I added a user to this profile with the security role "Salesperson".

    Now, I tested the different possibilities within the Field Permissions tab of this specific security profile field. Everything works well except when I set Read and Update to YES and Create to NO. The user is still able to fill in the field if this field is empty.

    How can I solve this?

    Last question: if I don't give read persmissions to this field then the user still sees it but the value is encrypted. Can't we just "hide" the field for all users of this field security profile?

     

    Regards,


    Sven8E
    Thursday, November 24, 2011 8:16 AM

Answers

  • Create does not mean add a value to field that did not have value before. I believe it means when you are creating a record do you have access to the attribute.

    By setting the Create to No, you would not have access to this field when creating a new record. But with Read and Update set to yes, the user has the privilege to see the values held in this field and with the Update permission also update the value of the field even if no value existed earlier.

    The default functionality is to return encrypted value. However, through custom scripting you can hide the fields on the form. But in that case, it would involve complex code of first retrieving when a user has permission to the field and if no then hiding the field.

    HTH

    Sam


    Web: http://www.inogic.com
    Blog: http://inogic.blogspot.com
    Email: news@inogic.com
    If you find this post helpful then please "Vote as Helpful" and "Mark As Answer".
    • Proposed as answer by Sam - Inogic Thursday, November 24, 2011 10:38 AM
    • Marked as answer by Sven8E Thursday, November 24, 2011 12:37 PM
    Thursday, November 24, 2011 10:38 AM