应用到: CRM 2015 on-prem, CRM Online
Contains the data that is needed to add a set of existing privileges to an existing role.
命名空间: Microsoft.Crm.Sdk.Messages
程序集: Microsoft.Crm.Sdk.Proxy (在 Microsoft.Crm.Sdk.Proxy.dll 中)
语法
声明
<DataContractAttribute(Namespace:="https://schemas.microsoft.com/crm/2011/Contracts")> _
Public NotInheritable Class AddPrivilegesRoleRequest
Inherits OrganizationRequest
[DataContractAttribute(Namespace="https://schemas.microsoft.com/crm/2011/Contracts")]
public sealed class AddPrivilegesRoleRequest : OrganizationRequest
示例
The following example shows how to use this message. For this sample to work correctly, you must be connected to the server to get an IOrganizationService接口。有关完整示例,请参阅本主题后面的链接。
// Add the prvReadAccount privilege to the example roles to assure the
// team can read accounts.
AddPrivilegesRoleRequest addPrivilegesRequest = new AddPrivilegesRoleRequest
{
RoleId = _roleId,
Privileges = new[]
{
// Grant prvReadAccount privilege.
new RolePrivilege
{
PrivilegeId = readAccountPrivilege.Id
}
}
};
_service.Execute(addPrivilegesRequest);
备注
Message Availability
若要使此消息正常工作,调用方必须连接到服务器。
Usage
Pass an instance of this class to the Execute method, which returns an instance of the AddPrivilegesRoleResponse class.
Privileges and Access Rights
To perform this action, the caller must have privileges on the Role entity and access rights on the specified record in the RoleId property. For a complete list of the required privileges, see AddPrivilegesRole Privileges.
继承层次结构
System.Object
Microsoft.Xrm.Sdk.OrganizationRequest
Microsoft.Crm.Sdk.Messages.AddPrivilegesRoleRequest
线程安全性
此类型的所有公共静态(Visual Basic 中的 Shared)成员都是线程安全成员。不保证任何实例成员是线程安全成员。
平台
开发平台
Windows Vista、Windows Server 2003 和
目标平台
Windows Vista,Windows XP
Change History
另请参阅
参考
AddPrivilegesRoleRequest 成员
Microsoft.Crm.Sdk.Messages 命名空间
AddPrivilegesRoleResponse
其他资源
Privilege and Role Entities
Role Entity Messages and Methods
Privilege Entity Messages and Methods
Sample: Assign a Record to a Team
AddPrivilegesRole Privileges
Send comments about this topic to Microsoft.
© 2014 Microsoft Corporation. All rights reserved.