CRM 2013 field level security issue/bug? RRS feed

  • Question

  • The issue arises whilst trying to update a record that has a field with field level security turned on, but was created BEFORE the field was added to the entity.


    Create and Save a Record - RecordA

    Add a new field (booleon) to the entity with field level security on, default the value to be No

    Create and Save a Record – RecordB with the Boolean field left as default - No

    Create and Save a Record – RecordA with the Boolean field set to Yes

    Quering the database at this point would show the following

    Record Name, field

    RecordA, null

    RecordB, 0

    RecordC, 1

    If you now try to open/save/change status of RecordA with a user which doesn’t have a field level security profile to that field then it fails, the record is then unusable until you assign the user permission to UPDATE the field.

    It seems CRM is trying to set the NULL records to 0 (default) even though the user doesn't have permission to in the security profiles.

    As its CRM Online, whats the best way to update all the null values to 0 without effecting the modifiedon dates?



    Monday, January 27, 2014 4:10 PM


All replies