Author: Nishant Rana

I love working in and sharing everything about Microsoft.NET technology !

Use OptionSet Wrapper component to show color-coded options on the form – Model-driven apps/ Dynamics 365


We can make use of the OptionSet Wrapper component to show color-coded options on the form for the choices or option set fields.

Below we have added the Option Set wrapper component to the Rating field of the lead in the Lead (Main) form.

We can see the field added but do not see any colors for it.

A screenshot of a contact form Description automatically generated

This is because it uses the color defined for that column, which wasn’t defined out of the box for that field.

We then defined the colors as shown below for different choices / options.

After saving and publishing our changes, we were able to see the corresponding color for the choices.

A screenshot of a computer Description automatically generated

Also check –

Hope it helps..

Advertisements

New Lead Qualification Experience – Dynamics 365 Sales


To enable the new lead experience, navigate to App Settings >> Lead + opportunity management in the Sales Hub App.

A screenshot of a computer Description automatically generated

On enabling it, we get the option to specify whether the Account, Contact, and Opportunity records are created automatically or the user (seller) has the option to specify which record to create.

We also see the option to Copilot summarizing the case once a lead is qualified.

For opportunity, if we select Seller, we get an additional option to modify the Opportunity form by adding or removing fields and also the option to allow a maximum of 5 new opportunities during lead qualification.

A screenshot of a computer Description automatically generated

Clicking on the Add or remove fields link opens the Opportunity qualify lead form for customization.

A screenshot of a computer Description automatically generated

Let us see it in action.

On clicking the Qualify command, we can see the new Qualify lead dialog opened in the side pane.

It gives us the option to create a new Account, Contact, and/or Opportunity record.

A screenshot of a computer Description automatically generated

For Account and Contact, we can specify an existing record or select none if we do not want the Account and Contact record to be created.

A screenshot of a computer Description automatically generated

For opportunity, we can click on edit icon to update the details of the opportunity record to be created. It will open the Opportunity qualify lead form.

A screenshot of a computer Description automatically generated

Similarly clicking on + New opportunity allows us to specify a value for the new opportunity record.

A screenshot of a computer Description automatically generated

As we had selected the option of a maximum of 5 opportunities, we got the below message on trying to specify the 6th opportunity record.

“You can’t add more than 5 opportunities.”

A screenshot of a computer Description automatically generated

Let us click on Qualify.

We can see below details, the link to the records generated, and the summary.

A screenshot of a computer screen Description automatically generated

Clicking on Finish opens the 1st opportunity record. We can also see the summary added to it.

A screenshot of a computer Description automatically generated

On setting all the options to Automatic,

A screenshot of a computer Description automatically generated

we can see the below details in the Qualify lead dialog, all as read-only information.

Get all the details here

Hope it helps..

Advertisements

Bypass Power Automate Flows using SuppressCallbackRegistrationExpanderJob optional parameter – Dataverse / Dynamics 365


Using the SuppressCallbackRegistrationExpanderJob optional parameter in our Request object, we can bypass the execution of the flows registered against that particular event/trigger.

We have a flow registered on the update event of the lead record.

Now let us create a lead record through SDK.

A screen shot of a computer code Description automatically generated

We can see our flow triggered.

A screenshot of a computer Description automatically generated

Now let us add the optional parameter SuppressCallbackRegistrationExpanderJob and check

A screen shot of a computer code Description automatically generated

This time as expected our lead record was created but the flow was not triggered.

A screenshot of a computer Description automatically generated

Also check –

Using BypassBusinessLogicExecution Parameter (Preview) to bypass Custom Sync and Async Logic (Plugin and Workflow)

Bypass execution of specific plugin (step) using BypassBusinessLogicExecutionStepIds parameter

Hope it helps..

Advertisements

Sample Code to create and associate Folder / SharePoint Document Location (Dataverse /Dynamics 365 / SharePoint Online)


Below is our sample record for a custom table custom_contract for which we will be creating the folder in SharePoint and associated it with this record using the SharePoint Document Location record. We’d use the same naming pattern that CRM uses i.e. Name + ”_” + ”GUID”

A screenshot of a chat Description automatically generated

Below we have passed the details of the record along with CrmServiceClient and SharePoint’s client context.

A screenshot of a computer code Description automatically generated

The below code will first check if there is already a SharePoint Document Location created by CRM using ends with GUID condition. If it doesn’t exist, we are using the name field plus GUID of the record to create the folder in SharePoint and then associate using SharePoint Document Location record. Also we have used Regex to make sure we replace the special characters with “-“ similar to what CRM does. We are also checking if the Folder exists with that name in SharePoint before creating one.

Below is the GUID / record we have specified while creating the SharePoint Document Location record, the SharePoint Document location configured for that particular table.

A screenshot of a computer Description automatically generated

The sample code – 

  var authManager = new AuthenticationManager(applicationId, certPath, password, domain);
            ClientContext clientContext = authManager.GetContext(siteUrl);

            var serviceClient = new CrmServiceClient(connection);
            if (serviceClient.IsReady == true)
            {
                var myCRMRecord = serviceClient.Retrieve("custom_contract", 
                    new Guid("f655304e-045b-ef11-bfe2-000d3a9b4e06"), new ColumnSet("custom_name"));
                CheckIfShareDocLocationExistElseCreateandAssociate(myCRMRecord, serviceClient, clientContext);
            }


 private static void CheckIfShareDocLocationExistElseCreateandAssociate(Entity myCrmRecord, CrmServiceClient serviceClient, ClientContext clientContext)
        {
            var querySharePointDocumentLocation = new QueryExpression("sharepointdocumentlocation");
            querySharePointDocumentLocation.ColumnSet.AddColumns("name", "relativeurl", "parentsiteorlocation", "regardingobjectid");
            querySharePointDocumentLocation.Criteria.AddCondition("regardingobjectid", ConditionOperator.Equal, myCrmRecord.Id);
            querySharePointDocumentLocation.Criteria.AddCondition("relativeurl", ConditionOperator.EndsWith, myCrmRecord.Id);
            var result = serviceClient.RetrieveMultiple(querySharePointDocumentLocation);
            if (result.Entities.Count == 0)
            {                
                var folderName = myCrmRecord.Attributes["custom_name"].ToString();
                // this makes sure we replace the special characters with - similar to what CRM does when autocreating the record.
                string regexPattern = @"[~#%&*:<>?/\\{|}.""-]";
                string replacement = "-";
                folderName = Regex.Replace(folderName, regexPattern, replacement) + "_" + myCrmRecord.Id.ToString().ToUpper();
                var folderRelativeURL = "custom_contract/" + folderName;

                Web currentWeb = clientContext.Web;
                var folderExists = currentWeb.DoesFolderExists(folderRelativeURL);
                if (!folderExists)
                {
                    var list = clientContext.Web.Lists.GetByTitle("Documents");
                    list.RootFolder.Folders.Add(folderRelativeURL);
                    clientContext.ExecuteQuery();
                }

                var documentLocation = new Entity("sharepointdocumentlocation");
                documentLocation["name"] = "Documents on Default Site 1";
                documentLocation["relativeurl"] = folderName;
                // specifying the GUID of the SharePoint Document Location configured for that table
                documentLocation["parentsiteorlocation"] = new EntityReference("sharepointdocumentlocation", new Guid("cf97e6d8-0b4e-ef11-a317-6045bdd74f46"));
                documentLocation["regardingobjectid"] = new EntityReference("custom_contract", myCrmRecord.Id);
                serviceClient.Create(documentLocation);
            }
        }

The result –

A screenshot of a computer Description automatically generated

Also refer –

Hope it helps..

Advertisements

Fixed – The attempted operation is prohibited because it exceeds the list view threshold error– SharePoint Online


While trying to load all the files in a particular folder for processing, we got the below error

The attempted operation is prohibited because it exceeds the list view threshold – Microsoft.SharePoint.SPQueryThrottledException

The folder we were targeting contained 25K files in it. (the default threshold – 5000 items)

So we updated our code to make use of CamlQuery to retrieve the files in batch along with the listitemcollectionpostion object to loop and process through all the files.

Below is the sample code for reference – 

var applicationId = "d7eaeeb7-ef0a-474d-9b94-567013576c14";
var password = "password";
var domain = "xyz.onmicrosoft.com";
var siteUrl = "https://xyz.sharepoint.com/sites/MyTeamSite";
var certPath = @"C:\SharePointApp\MyTestCertificate.pfx";
var folderRelativeUrl = "xyz/correspondences";
      
  var authManager = new AuthenticationManager(applicationId, certPath, password, domain);
        ClientContext clientContext = authManager.GetContext(siteUrl);
        var folder = clientContext.Web.GetFolderByServerRelativeUrl(folderRelativeUrl);
        clientContext.Load(folder);

        // replaced it with usage of CamlQuery
        //context.Load(folder.Files);
        //context.ExecuteQuery();

        ListItemCollectionPosition position = null;
        do
        {
            CamlQuery camlQuery = new CamlQuery
            {
                ViewXml = $@"<View Scope='RecursiveAll'>
                    <Query>                          
                        <OrderBy>
                            <FieldRef Name='ID' Ascending='TRUE'/>
                        </OrderBy>
                    </Query>
                    <RowLimit>500</RowLimit>
                </View>",
                ListItemCollectionPosition = position
            };

            var listItems = folder.ListItemAllFields.ParentList.GetItems(camlQuery);
            clientContext.Load(listItems);
            clientContext.ExecuteQuery();
            position = listItems.ListItemCollectionPosition;

            foreach (ListItem listItem in listItems)
            {
                // To process only the files (not folder)
                if (listItem.FileSystemObjectType == FileSystemObjectType.File)
                {
                    var file = listItem.File;
                    clientContext.Load(file);
                    clientContext.ExecuteQuery();
                    ProcessFiles(file);
                }
            }
        } while (position != null);

Also refer –

https://nishantrana.me/2024/07/30/calling-sharepoint-online-api-using-azure-ad-app-only-permissions-using-certificate-auth/

https://nishantrana.me/2024/07/31/sample-code-to-check-if-a-folder-exists-else-create-it-sharepoint-online-pnp-framework-c/

https://nishantrana.me/2024/08/01/fixed-access-denied-cryptographicexception-on-calling-sharepoint-online-apis-using-azure-ad-app-only/

Hope it helps..

Advertisements

Fixed – “The relative url contains invalid characters. Please use a different name. Valid relative url names cannot ends with the following strings: .aspx, .ashx, .asmx, .svc , cannot begin or end with a dot, cannot contain consecutive dots and cannot contain any of the following characters: ~ ” # % & * : ? / \ { | }. “ error while creating SharePoint Document Location – Dynamics 365 / Dataverse


We were using the below code to create a sharepointdoucmentlocation record through a C# Console App.

        private void CreateAssociateSharePointDocumentLocation(string folderName, Guid recordGuid, ServiceClient serviceClient)
        {            
            var documentLocation = new Entity("sharepointdocumentlocation");
            documentLocation["name"] = "Documents on Default Site 1";
            documentLocation["relativeurl"] = folderName;
            documentLocation["parentsiteorlocation"] = new EntityReference("sharepointdocumentlocation", new Guid(parentSiteorLocation));
            documentLocation["regardingobjectid"] = new EntityReference("schemanametable", recordGuid);
            serviceClient.Create(documentLocation);
        }

For folderName we were using the below format, similar to what CRM does, when someone opens the document tab for the record, to create the sharepointdocument location record.

{name} + “_” + {GUID}

However, while creating one particular record we got the below error which was because the name field had “&” in it.

The relative URL contains invalid characters. Please use a different name. Valid relative url names cannot end with the following strings: .aspx, .ashx, .asmx, .svc, cannot begin or end with a dot, cannot contain consecutive dots, and cannot contain any of the following characters: ~ ” # % & * : ? / \ { | }.

A screenshot of a computer Description automatically generated

As the error message suggests we need to either remove/replace the special characters in the name field before creating the folder in SharePoint and associating it with the SharePoint Document Location record in the CRM.

Sample code to check if a Folder exists else create it (SharePoint Online / PnP Framework / C#)

Say for e.g. we have the following record having the name as

“..N ” I & S * H : A | N T.aspx .ashx..”

CRM / Dynamics 365 will create the corresponding folder and SharePoint document location record for it.

A screenshot of a computer Description automatically generated

The folder created will have all the special characters replaced with “–“ and suffixed with GUID of the record.

–N – I – S – H – A – N T-aspx -ashx–_03DED211E259EF11BFE2000D3A9B4E06

So if we are creating the folder / SharePoint document location record through code (C#), we can use the below Regular Expression to do the same.

 string myNameField = "..N \" I & S * H : A | N T.aspx.ashx..";
            string regexPattern = @"[~#%&*:<>?/\\{|}.""-]";
            string replacement = "-";
            string result = Regex.Replace(myNameField, regexPattern, replacement);

            Console.WriteLine("Original: " + myNameField);
            Console.WriteLine("Modified: " + result);
            Console.ReadLine();

Hope it helps..

Advertisements