Microsoft Dynamics CRM (Archived)

Field security in CRM 2011

(0) Share

Report

Posted on by Birgit RD

Hi,

We are migrating an application from dynamics 2011 to dynamics 2016 v8.2

For contact we have an issue with the security on field level. The field is a custom field.

In 2016, one of our plugins throws an error because lack of permission due to field level security.

In 2011, the same functionality works fine.

As I don't have any experience with dynamics 2011, I was wondering if plugins were already taking into account the field level security or if this was added later and hence could explain the difference?

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Hi Birgit,

Field Level Security was introduced in Dynamics CRM 2011, so it is possible that this was already implemented earlier.

It is possible that the logic was there earlier, but can you please provide additional details about the error that you are getting, such as the exact message and possibly the log file.

That will help troubleshoot the exact issue.

Was this reply helpful? Yes No
Suggested answer

Shahbaaz Ansari 6,211 on at

Like (0)

Report

Hi RD,

The user who is calling the plugin, having the read permission of that field?? if not please try enabling field level security for that user and try if it resolve's your issue.

Best Regards,

Shahbaaz

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Hi,

Create one new field level security profile in CRM 2016 . In the created profile you can see all the secured fields . Give the access of the particular field and then the user in the field security profile.

You can refer below article how to create profile.

www.preact.co.uk/.../updated-field-security-profiles-dynamics-crm-2015

Was this reply helpful? Yes No
Birgit RD 2 on at

Like (0)

Report

The whole system is currently working in CRM 2011 with the same field security profile as in CRM 2016. These profiles are set up, and we cannot (are not allowed) change them.

The error specifies : user does not have Update permissions for the dos_abc attribute of entity contact.

So, it clearly points to FLS. But in that case, I would think we had the same in 2011.

I see in the pre-update that this attribute is removed in the plugin, and added again within the plugin.

I found following article, but not sure if I understand correctly that in 2011, the FLS is removed but removing and re-adding an attribute: stackoverflow.com/.../set-value-with-javascript-on-a-field-for-users-that-do-not-have-proper-field-lev

Was this reply helpful? Yes No
Suggested answer

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Hi Birgit,

It is possible that the users/teams that are assigned to the Field Security Profile in your 2011 environment are not assigned to the Field Security Profile in your 365 environment.

Have System Administrator user compare Users and Teams between both environments.

Hope this helps.

Was this reply helpful? Yes No
Birgit RD 2 on at

Like (0)

Report

The user has the same field security profile as in 2011.

We asked the Original developer what he had done in 2011 to make it work despite the field security. He says he had done nothing special.

I don't understand how it can work in 2011, but I have no experience in that version.

We fixed the issue as most suggested by adapting the field security profile and give extra permissions.

Thanks all for your feedback.

(I still feel a bit frustrated not understanding why t does work in 2011)

Was this reply helpful? Yes No
Verified answer

Birgit RD 2 on at

Like (0)

Report

Btw, in teh security profile, we gave create/update permissions as the plugin transfers data from one system to another. However Read access is not given as the user is not allowed to see some of the data.

Was this reply helpful? Yes No