Microsoft Dynamics CRM (Archived)

Using console program to change user role can't find SecurityPrincipal or TargetOwnedAccount

(0) Share

Report

Posted on by rthompson

1,532

I am using Microsoft Dynamics CRM 2016 SDK.

I am getting the following error messages.

The type or namespace name 'SecurityPrincipal' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'TargetOwnedAccount' could not be found (are you missing a using directive or an assembly reference?)

Here's my code.

using Microsoft.Crm.Sdk.Messages;

using Microsoft.Xrm.Sdk;
using Microsoft.Xrm.Sdk.Client;
using System;
using Microsoft.Xrm.Tooling.Connector;
using System.Configuration;
using System.Net;
using System.ServiceModel.Description;


namespace CrmSecurityRole
{
    class Program
    {
        static void Main(string[] args)
        {
            Uri crmUrl = new Uri(ConfigurationManager.AppSettings["CrmServerUrl"]);
            string userName = ConfigurationManager.AppSettings["UserName"];
            string password = ConfigurationManager.AppSettings["Password"];

            IOrganizationService service;
            // Get the CRM connection string and connect to the CRM Organization

            ClientCredentials credentials = new ClientCredentials();
            credentials.UserName.UserName = userName;
            credentials.UserName.Password = password;

            credentials.Windows.ClientCredential = System.Net.CredentialCache.DefaultNetworkCredentials;

            ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

            service = new OrganizationServiceProxy(crmUrl, null, credentials, null);

            // Create the SecurityPrincipal Object
            SecurityPrincipal principal = new SecurityPrincipal();

            principal.Type = SecurityPrincipalType.User;

            // PrincipalId is the Guid of the user to whom access is being granted
            principal.PrincipalId = new Guid("7B222F98-F48A-4AED-9D09-77A19CB6EE82");

            // Create the PrincipalAccess Object
            PrincipalAccess principalAccess = new PrincipalAccess();

            // Set the PrincipalAccess Object's Properties
            principalAccess.Principal = principal;

            // Gives the principal access to read
            principalAccess.AccessMask = AccessRights.ReadAccess;

            // Create the Target Object for the Request
            TargetOwnedAccount target = new TargetOwnedAccount();

            // EntityId is the Guid of the account access is being granted to
            target.EntityId = new Guid("6A92D3AE-A9C9-4E44-9FA6-F3D5643753C1");

            // Create the Request Object
            GrantAccessRequest grant = new GrantAccessRequest();

            // Set the Request Object's properties
            grant.PrincipalAccess = principalAccess;
            grant.Target = target;

            // Execute the Request
            GrantAccessResponse granted = (GrantAccessResponse)service.Execute(grant);

        }
    }
}

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (1)

Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Try to include below namespace-

Namespace: Microsoft.Crm.Sdk.Messages

[View:https://msdn.microsoft.com/en-us/library/microsoft.crm.sdk.messages.principalaccess.aspx]

Was this reply helpful? Yes No
rthompson 1,532 on at

Like (0)

Report

Hi Goutam,

That namespace is not working.

From the examples that I have seem the name space should be Microsoft.Crm.Sdk.Messages.

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Yes it was copy paste mistake now I have corrected.

Was this reply helpful? Yes No
rthompson 1,532 on at

Like (0)

Report

Still getting the same error messages.

Was this reply helpful? Yes No
Suggested answer

Emre GULCAN 2,379 on at

Like (0)

Report

Hi,

Probably your code (or sample code that you copied) using EarlyBound class structure. If you want to use EarlyBound class structure in your code/solution, you need to create this EarlyBound class. You can use XrmToolBox 's Early Bound Generator plugin (https://www.xrmtoolbox.com/plugins/DLaB.Xrm.EarlyBoundGenerator/) or directly use CrmSvcUtil.exe inside console, details are here https://msdn.microsoft.com/en-us/library/gg327844.aspx

You can also find "latebound" sample code https://github.com/emregulcan/xrmlibrary.2016/blob/dc1ffeaa5239c5b7da6b06fa79d534c4848a5409/XrmLibrary.EntityHelpers/Common/CommonHelper.cs#L330-L338

Was this reply helpful? Yes No
rthompson 1,532 on at

Like (0)

Report

Before I go down this road. Any suggestion on what is the right way to go?

Was this reply helpful? Yes No
Suggested answer

Emre GULCAN 2,379 on at

Like (0)

Report

Hi,

There is no limitations for using LateBound or EarlyBound entities to develop any application / plugin for Dynamics 365.

I prefer LateBound entity structure, because it's not depended anything and if you add a new attribute to Dynamics 365 entity, you can easily add this to your code block.

If you use EarlyBound entity structure, you have to re-generate earlybound class to get your new attribute inside your code.

in C#;

LateBound

- works like Dictionary (entity["firstname"] = "Emre"; )

- probably (if you're new bee) you can do mistakes when typing entity / attribute names or attribute types

EarlyBound

- it's a C# class and contains all attributes as Property (for exp. Account.Name)

- you can not do any mistake when typing entity / attribute names or attribute types

- few developers telling EarlyBound improves runtime performance, but I don't have any idea and test results.

- it requirement additional space in your code. if you do mistake to get all entities / atributes inside your EarlyBound class, probably it'll approx. 10 MB class.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Well, each has its own pros and cons. Performance wise late bound is better because CRM converts Early bound to late bound internally as the CLR only understands late bound.

Please refer to this article. (https://msdn.microsoft.com/en-us/library/gg509027.aspx#Performance)

Use early-bound types

Use the Entity class when your code must work on entities and attributes that aren’t known at the time the code is written. In addition, if your custom code works with thousands of entity records, use of the Entity class results in slightly better performance than the early-bound entity types. However, this flexibility has a disadvantage because you cannot verify entity and attribute names at compile time. If your entities are already defined at code time and slight performance degradation is acceptable, you should use the early-bound types that you can generate by using the CrmSvcUtil tool. More information: Use the early bound entity classes in code

Was this reply helpful? Yes No
rthompson 1,532 on at

Like (0)

Report

Okay.

Now that I understand early and late binding. I am still trying to understand why the 2 classes do not appear in the namespace Microsoft.Crm.Sdk.Messages.

The type or namespace name 'SecurityPrincipal' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'TargetOwnedAccount' could not be found (are you missing a using directive or an assembly reference?)

SDK 2016

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi Thompson,

I doubt that you are referring to obsolete code.

Security Principal and TargetOwnedAccount were part of CRM 4.0. I highly doubt if they are still valid anymore.

Was this reply helpful? Yes No