Unanswered

Field cannot be secured

(0) Share

Report

Posted on by RobCNIE

Hi All,

I have a table with a field called bids. We would like to add field level security to this field so that members of our aggregators team cannot read or update the field. I have enabled column level security against the field and made a column security profile, added the team and set the permissions. I then published all the customisations in my dev environment (unmanaged).

The problem I have is that this table already exists in my forward environments (test, pre-prod, and prod - all managed) and when I try to deploy, using either export / import or pipelines, I get the error: "The field: bids is not securable". I have done some extensive searching and it seems that there is not much info out there on this, other than someone mentioned you cant retroactively change a column to use FLS if its already deployed to a managed solution. Is this correct? Do I need to delete the column, re-deploy and re-add? Seems a tad nuclear!?

Has anyone else found this problem and are there any work arounds?

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

LaurenWithers 82 on at

Like (0)

Report

Hey, unfortunately I believe that once a field has been added to a managed solution, it cannot be retroactively changed to use field level security. This means that if you add FLS to a field that already exists in a managed solution, you will not be able to deploy the change to an upstream environment. Yep, a workaround would be to manually remove the field from the managed solution, add field level security to the field in your dev environment, and then re-add/deploy the field to the managed solution before deploying to the test/prod environments. However deleting and re-adding fields is risky if the field is being used in other parts of the solution.

Let me know if this helped with a thumbs up 🙂

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @RobCNIE,

At first @LaurenWithers gave me a doubt but I double checked and it's possible to enabled column/field level security after the column was created in the target environments (env) for both an unmanaged or managed solution. Is that table and field part of a 1st/3rd party solution? If not, my guess is at some point that field/column got deleted in the Dev env and is no longer matching the expected settings in the target/forward envs. I would try to create a new temp solution in one of your forward envs (eg Test), add only that field to the solution and import it back to your Dev env (you'll need to delete the field in Dev first). Once it back there, enable FLS.
Hope this helps!

Was this reply helpful? Yes No