Security Role Privilege to Change Business Unit in MS CRM:

There’s a strong possibility that an Administrator working with an implementation using a complex business unit structure would want to include that structure in a solution to be exported as a managed or unmanaged solution. This would allow them to make changes to the business unit structure in their DEV environment, and then import those changes into the production environment after they’ve been tested, just like they would a change to a script, a plugin, an entity configuration, or a security role. However, BUs are not one of the items that can be added to a solution.

Let’s say User1 who wants to change the BU of User2 who is under same BU or different BU, User1 should have minimal Organization level privilege on below entities and can be configured by selecting 

CRM Application à Settings à Administration à Security Roles à Open the corresponding Security Role  à Give below privileges for ‘System Job” in “Customization” tab, Calender in “Service Management” tab and other below entities privileges in “Core Records” tab

1. System Job – Append , Create, Delete, Share
2. Calender – Read, Write
3. Follow – Append , Create
4. Email Template – Assign , Share
5. Customer Relationship – Delete
6. Executable Workflow Jobs in “Miscellaneous Privileges” section in the “Customization” tab

The below screen shots show the security role privileges highlighted in red.

Cheers,

Arun

Avoid hardcoding - Early binding types in CRM 2011/2013 Plugins 

Early bound classes will contains the objects of entities in which it can be used to do the CRUD operation etc. in which it will give all the attribute values as well. But however, if checking for entity.Attributes.Contains like the below example, usually most of the developers uses hardcoding the attribute schema names.

protected void ExecuteTestPlugin(LocalPluginContext localContext)

        {

            if (localContext == null)

            {

                throw new ArgumentNullException("localContext");

            }

            IPluginExecutionContext context = localContext.PluginExecutionContext;

            IOrganizationService service = localContext.OrganizationService;

            XrmServiceContext sContext = new XrmServiceContext (service);

            Opportunity opportunity = ((Entity)context.InputParameters["Target"]).ToEntity< XrmServiceContext >();

if (pluginContext.MessageName.ToLowerInvariant() == "update")

            {

                if (opportunity.Attributes.Contains("name")

                {

                    //To do Business logic

                }

            }

}

Instead of highlighted code, the hardcoded values can be avoided by using the reflection concept as below.

Create a class which should have the following methods.

public class CommonFramework

    {

public string ReflectionPropertyName<T>(Expression<Func<T>> expression)

        {

            MemberExpression member = (MemberExpression)expression.Body;

            return member.Member.Name.ToLower();

 }

     }

Consume the above class in the highlighted area to avoid hardcoding.

if (pluginContext.MessageName.ToLowerInvariant() == "update")

            {

                if (opportunity.Attributes.Contains(new CommonFramework().ReflectionPropertyName(() => opportunity.EstimatedCloseDate)))

                {

                    //To do business logic

                }

            }

}

Happy Coding :)

OrganizationServiceProxy in CRM 2011/2013 Plugins to use Early binding.

CRM 2011/2013 had an option to create a plugins using Early binding or Late bindings.

If late binding is used, then the attributes values should be hardcoded or create a constant class that contains the attribute names to achieve it.

Early bound classes will contains the objects of entities in which it can be used to do the CRUD operation etc. and there is no need of hardcoding the attribute names. There are advantages and disadvantages working with Early and Late binding. But I am not going to explain in this blog. The below blogs will gives more information on overview, differences and how to use it.

http://woodsworkblog.wordpress.com/2013/02/25/crm-2011-early-binding-vs-late-binding-performance/

http://www.magnetismsolutions.com/blog/roshanmehta/2012/05/04/dynamics_crm_2011_early_vs._late_binding_overview

To use early bound types in a CRM2011 plugin and enable this, It should either be add a ProxyTypesBeavior(), or set .EnableProxyTypes. However, both of these properties apply to an OrganizationServiceProxy class, and do not exist on the IOrganizationService interface.

So if it uses IOrganizationService and try to do the CRM transactions like the below, it fails in the highlighted red color  in the bewlow example with an error “Attribute regardingobjecttypecode must not be NULL if attribute regardingobjectid is not NULL”

protected void ExecuteTestPlugin(LocalPluginContext localContext)

        {

            if (localContext == null)

            {

                throw new ArgumentNullException("localContext");

            }

            IPluginExecutionContext context = localContext.PluginExecutionContext;

            IOrganizationService service = localContext.OrganizationService;

            XrmServiceContext sContext = new XrmServiceContext (service);

            Opportunity opportunity = ((Entity)context.InputParameters["Target"]).ToEntity< XrmServiceContext >();

            try

            {

                //to do business logic

Opportunity opp = new Opportunity()

                {

                    Name = “bla  bla bla”,

                    OpportunityId = opportunityClose.OpportunityId.Id

                };

                service.Update(opp);//Fail in this part

            }

            catch (FaultException<OrganizationServiceFault> e)

            {

                new InvalidPluginExecutionException("Error Test Plugin : " + e);

                throw;

            }

            catch (Exception e)

            {

                new InvalidPluginExecutionException("Error Test Plugin : " + e);

                throw;

            }

        }

To avoid this error, there is a below work around which will work like a charm.

If the Plugin project created using Developer tool kit, then in the “Plugin.cs” class, the below highlighted code should be added.

   internal LocalPluginContext(IServiceProvider serviceProvider)

            {

                if (serviceProvider == null)

                {

                    throw new ArgumentNullException("serviceProvider");

                }

                // Obtain the execution context service from the service provider.

                this.PluginExecutionContext = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));

                // Obtain the tracing service from the service provider.

                this.TracingService = (ITracingService)serviceProvider.GetService(typeof(ITracingService));

                // Obtain the Organization Service factory service from the service provider

                IOrganizationServiceFactory factory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));

                factory.GetType().GetProperty("ProxyTypesAssembly").SetValue(factory, typeof(XrmServiceContext).Assembly, null);

                // Use the factory to generate the Organization Service.

                this.OrganizationService = factory.CreateOrganizationService(this.PluginExecutionContext.UserId);

               

            }

Happy Coding :)