Blog

1. What is editable grid?

2. Once you set up editable grid for an entity, can you still use the traditional read only views?

3. Can it be used on out of the box and custom entities?

4. Can it be used on personal views?

5. Can it be used on mobile clients?

6. Can you apply it to just some view on an entity and not others?

7. How do you set it up?

8. What can you do on an editable grid?

9. What can’t you do on an editable grid?

Change a value on a field of a parent entity, e.g. phone number of parent account on an editable grid of contacts. As you can see below, it’s locked:

10. Can you set an entity to default to editable or read only grid?

CHART ARE USED TO QUICKLY VIEW THE  INFORMATION.

COLUMN CHART
BAR CHART
AREA CHART
LINE CHART
PIE CHART
FUNNEL CHART
MULTI-SERIES CHART
COMPARISON CHART(STACKED CHART)
TAG CHART
DOUGHNUT CHART

Create a new field  optionset as approval status on  opportunity entity with optionset values as
 Submitted                  =   100000000 
 Pending approval     =    100000001 
 Approved                 =      100000002

1)Condition when Approval status changes from Pending approval to Approved.

2)Share the record with  a system  user  with  read access only.

3)Find out how to share the record to system user using plugin….. 

#GrantaccessRequest 
#PostImage

I am using Developer toolkit for visual studio 2013 for this plugin.. 

Plugin code here

// <copyright file=”PostOperationopportunityUpdate.cs” company=””>
// Copyright (c) 2017 All Rights Reserved
// </copyright>
// <author></author>
// <date>3/16/2017 5:10:33 PM</date>
// <summary>Implements the PostOperationopportunityUpdate Plugin.</summary>
// <auto-generated>
//     This code was generated by a tool.
//     Runtime Version:4.0.30319.1
// </auto-generated>

using System;
using System.ServiceModel;
using Microsoft.Crm.Sdk.Messages;
using Microsoft.Xrm.Sdk;
using Microsoft.Xrm.Sdk.Query;

namespace CrmPackage1.Plugins1
{

    /// <summary>
    /// PostOperationopportunityUpdate Plugin.
    /// Fires when the following attributes are updated:
    /// new_approvalstatus
    /// </summary>    
    public class PostOperationopportunityUpdate : PluginBase
    {
        /// <summary>
        /// Initializes a new instance of the <see cref=”PostOperationopportunityUpdate”/> class.
        /// </summary>
        /// <param name=”unsecure”>Contains public (unsecured) configuration information.</param>
        /// <param name=”secure”>Contains non-public (secured) configuration information. 
        /// When using Microsoft Dynamics 365 for Outlook with Offline Access, 
        /// the secure string is not passed to a plug-in that executes while the client is offline.</param>
        public PostOperationopportunityUpdate(string unsecure, string secure)
            : base(typeof(PostOperationopportunityUpdate))
        {

            // TODO: Implement your custom configuration handling.
        }


        /// <summary>
        /// Main entry point for he business logic that the plug-in is to execute.
        /// </summary>
        /// <param name=”localContext”>The <see cref=”LocalPluginContext”/> which contains the
        /// <see cref=”IPluginExecutionContext”/>,
        /// <see cref=”IOrganizationService”/>
        /// and <see cref=”ITracingService”/>
        /// </param>
        /// <remarks>
        /// For improved performance, Microsoft Dynamics 365 caches plug-in instances.
        /// The plug-in’s Execute method should be written to be stateless as the constructor
        /// is not called for every invocation of the plug-in. Also, multiple system threads
        /// could execute the plug-in at the same time. All per invocation state information
        /// is stored in the context. This means that you should not use global variables in plug-ins.
        /// </remarks>
        protected override void ExecuteCrmPlugin(LocalPluginContext localContext)
        {
            if (localContext == null)
            {
                throw new InvalidPluginExecutionException(“localContext”);
            }

            // TODO: Implement your custom Plug-in business logic.

            Entity opp = (Entity)localContext.PluginExecutionContext.InputParameters[“Target”];
           
            if (opp.LogicalName != “opportunity”)
                return;
            else
            {
                if (localContext.PluginExecutionContext.PostEntityImages.Contains(“PostImage”) && localContext.PluginExecutionContext.PostEntityImages[“PostImage”] is Entity)
                {
                  

                    Entity postImage = (Entity)localContext.PluginExecutionContext.PostEntityImages[“PostImage”];
                    if (postImage.Attributes.Contains(“new_approvalstatus”))
                    {
                        
                   //submitted->approved
                        //submitted->
                    OptionSetValue OPT = new OptionSetValue();
                    OPT = (OptionSetValue)postImage.Attributes[“new_approvalstatus”];
                    
                    //100000000
                    if (OPT.Value==100000002)
                    {
                        //Share record

                        #region get user details
                        String fetchXml = @”<fetch version=’1.0′ output-format=’xml-platform’ mapping=’logical’ distinct=’false’>
                                      <entity name=’systemuser’>
                                        <attribute name=’fullname’ />
                                        <attribute name=’businessunitid’ />
                                        <attribute name=’title’ />
                                        <attribute name=’address1_telephone1′ />
                                        <attribute name=’positionid’ />
                                        <attribute name=’systemuserid’ />
                                        <order attribute=’fullname’ descending=’false’ />
                                        <filter type=’and’>    
                                          <condition attribute=’internalemailaddress’ operator=’eq’ value=’dilipkumar@gmrltd.onmicrosoft.com’ />
                                        </filter>
                                      </entity>
                                    </fetch>”;
                        //THis will convert in Query base 
                        FetchExpression query = new FetchExpression(fetchXml);

                        EntityReference teamReference = new EntityReference();
                        EntityCollection entcollection = localContext.OrganizationService.RetrieveMultiple(query);

                        for (int i = 0; i < entcollection.Entities.Count; i++)
                        {
                             teamReference = new EntityReference(“systemuser”, entcollection.Entities[i].Id);

                        }
                        #endregion

                        #region Share record with read access
                        GrantAccessRequest grantAccessRequest = new GrantAccessRequest();
                        grantAccessRequest.Target = new EntityReference(opp.LogicalName, opp.Id);

                        PrincipalAccess principalAccess = new PrincipalAccess();
                        principalAccess.AccessMask = AccessRights.ReadAccess;
                        principalAccess.Principal = teamReference;

                        grantAccessRequest.PrincipalAccess = principalAccess;

                        GrantAccessResponse grantAccessResponse = (GrantAccessResponse)localContext.OrganizationService.Execute(grantAccessRequest);
                        #endregion
                    }
                    }
                    else
                    {
                        return;
                    }
                }
            }
        }
    }
}