Applies to Product - Power Platform Administration
What’s happening?
Customers are experiencing issues where the values for reading, updating, and creating permissions of the "Column Security Profile" are set to "N/A" when importing solutions from the development environment to the validation environment.
Reason:
The underlying cause of this is that the "CanBeSecuredFor*" tag added to the customization.xml file indicates whether a column can have column-level security applied, but it does not confirm if the column-level security is actually set. Therefore, even if this tag is present, it does not automatically configure the column-level security during the import process.
Resolution:
- Ensure that the "CanBeSecuredFor*" tag is correctly added to the customization.xml file.
- Understand that adding this tag allows the import to proceed without errors, but it does not guarantee that column-level security will be applied.