Issues & Changes
-
#37 Support Impersonation
-
#38 Deployment mandatory with Register-CrmPluginStep
-
#39 Add features for (Access) Teams
-
#40 Manage Roles and Privileges
-
#41 Add Application User
-
Update to latest supported framework and packages
- Microsoft.CrmSdk.XrmTooling.CoreAssembly 9.1.0.92
Impersonation
Use Use-CrmImpersonatedUser or Set-CrmSession -ImpersonatedUserId to set the UserId of the user to impersonate. This update the session context connection and applies to all following requests. Set to Guid.Empty to stop the impersonation.
Using the commands sets both the CallerId for the OrganizationService as the CallerAADObjectId for the Web API.
Register-CrmPluginStep: Deployment parameter
The parameter Deployment was mandatory on Register-CrmPluginStep. This is changed to optional with the default value Both, as this is the value most will use.
Teams features
New and updated Cmdlets to support the latest Dataverse feature for Teams. This includes manage Team Templates, manage Azure AD connected Teams, and add and remove users for record Teams.
New and Updated Cmdlets are:
- New-CrmTeam
- Remove-CrmTeam
- Set-CrmTeam
- Get-CrmTeamTemplate
- New-CrmTeamTemplate
- Remove-CrmTeamTemplate
- Set-CrmTeamTemplate
- Add-CrmRecordTeamUser
- Remove-CrmRecordTeamUser
Security & Privileges
The library now has support to manage security and privileges with the following Cmdlets:
- Get-CrmContentAccess
- Get-CrmPrincipalPrivileges
- Get-CrmRolePrivileges
- Remove-CrmRolePrivilege
- Set-CrmRole
- Set-CrmRolePrivilege
- Test-CrmUserPrivilege
The New-CrmRole and Set-CrmRole Cmdlets also have the Inheritance parameter.
Application User
And last but not least the New-CrmApplication cmdlet is added to add an Azure App Registration (SPN) as Application User in Dataverse. All you have to provide is the AppId/ClientId.