User Review
( votes)Hello Everyone,
Today I am going to share my thoughts on the maintain security role privileges for better ALM solution import on Dataverse.
Let’s get’s started.
Let’s discuss maintaining security role previleges for better Application Lifecycle Management(ALM)
solution imports. When working with Power Platform and Dataverse managed solutions, it’s essential to handle security roles effectively.
Here are some key points:
1. Feature details:
When a Power Platform admin modifies security roles that are system predefined customizable or custom security role previously imported by a Dataverse managed solution, these customizations can be overwritten by importing an update to the managed solution containing those security roles or when the system refreshes these security roles.
With the new feature, the system will merge the predefined customizable security roles. custom security roles, and privileges with the updates made by the Power Platform admin in an environment. This way, preexisting updates won’t be overwritten.
2. Use Cases:
Application Lifecycle Management(ALM): This feature supports the ALM process by ensuring that security role privileges updates are honored after managed solution imports.
Custom Security Role: You can now allow custom security roles to be updated in partner-managed solutions.
Better Control: By merging security role changes, you have better control over the security model during solution imports.
3. Alternative Approaches:
Account Management: Consider using accounts managed by an admin or deployer team to import solutions.
ALM Integration: Explore ALM integration with GitHub actions or Power Platform Pipelines, where impersonated accounts handle solution imports.
Remember that the specific approach may vary based on your organization’s requirements and the type of solutions you’re working with. Always test thoroughly before implementing changes in a production environment.
That’s it for today.
I hope this helps
Malla Reddy Gurram(@UK365GUY)
#365blogpostsin365days