Secured Field not in Field Security Profiles after upgrade to 9.0

(0) Share

Report

Posted on by Barbara Forsman

608

I have recently upgraded our Dynamics 365 Online to 9.0 in our sandbox. There is one secured field, pricelevelid from the Opportunity that is not included in the Field Security Profiles after the upgrade.

I have tried exporting the Field Security Profiles and the Opportunity entity from production to a solution and importing into the sandbox, but this field is still not included.

What do I need to do to get this field included in Field Security Profiles?

Will this happen in production if and when we get to the point of being ready to upgrade there?

Thanks in advance

Categories:

Upgrade

Security

I have the same question (0)

All responses (6)

Answers (2)

Abby Kong 6 on at

Like (0)

Report
Copy link

Link copied!

Hi Barbara,

If you go to Entity->Opportunity->Fields->Open field 'Price List'

Is the Field Security enabled inside?

Regards,

Abby

Was this reply helpful? Yes No
Barbara Forsman 608 on at

Like (0)

Report
Copy link

Link copied!

Thank you for your reply. I have tried to disable the security on the field, but I get

Field Security Profile Error

You must have sufficient permissions for a secured field before you can change its field level security. If you contact support, please provide the technical details.

The field is not read only on the form and is not locked on the form. I have sysadmin privileges, so what do I need to do to change the security on the field?

Thank you for your help!

Was this reply helpful? Yes No
Verified answer

MihirShah 4,038 on at

Like (0)

Report
Copy link

Link copied!

Hi,

If your field security is enabled you just have to edit the Field security profile to what you need it to be. Maybe you already know about it but here is a link to Field security profile

docs.microsoft.com/.../set-up-security-permissions-field

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Samething happens to me.

Was this reply helpful? Yes No
Barbara Forsman 608 on at

Like (0)

Report
Copy link

Link copied!

I think it may be caused by a business rule on the field. Our sandbox has been down for a week so I've not been able to test that theory.

Was this reply helpful? Yes No
Verified answer

Barbara Forsman 608 on at

Like (0)

Report
Copy link

Link copied!

Our sandbox is back up and running. I verified that deactivating the business rules allowed these fields to be included in Field Security Profiles. After I ensured the Field Security Profiles are correct, I activated the Business Rules again and all is well.

Was this reply helpful? Yes No