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.
We can see our flow triggered.
Now let us add the optional parameter SuppressCallbackRegistrationExpanderJob and check
This time as expected our lead record was created but the flow was not triggered.
There is a small enhancement added to the Lookup Control as part of Release Wave 2.
After performing a search for a specific record inside the Lookup Control dropdown menu, e.g. we have performed a search on “co*” on the Customer Lookup for Case.
We can press Enter to have the first item in the list selected.
We might see some of the custom actions not appearing in the Actions list inside the Perform Action step of the workflow.
This is because the Custom Action would be using one of the following parameter types, which is not supported for Perform Action like
Picklist (Optionset)
Entity
Entity Collection
E.g. we have the following actions defined few are bound to the Contact table, some are Global, and have different types specified as either Input or output parameter.
Out of the above actions defined, we can see only the following actions listed inside the perform actions step of the workflow.
The action which has input as Entity Reference are the ones listed, as it is one of the supported types. For the unsupported types, if used as an output parameter, the actions are listed.
Copilot (preview) for Dynamics 365 Customer Service provides the following features –
Case Summary
Conversation Summary
Ask a question
Write an email
Draft a chat response.
To enable it, navgiate to Customer Service Admin Center >> Agent Experience >> Productivity >> Manage (Copilot help pane and Summaries)
Check the required Copilot help pane settings and save.
Similarly for Summaries
For geographies outside the United States, to enable the Copilot features for Customer Service, we need to send an email to d365_csaipreview@microsoft.com with the Organization ID to enable the preview.
We can get the Organization ID from the Power Platform admin center for the environment.
As our environment was in the Australia region, we followed the same and within the next day, we got a response from Microsoft that it had been enabled in our Environment.
As per the email, the next step is to Enable copilots and generative AI features outside the US and Switzerland, for this again open the environment in the Power Platform admin center, and select Edit for Generative AI Features.
Check the Move data across regions option and enable it. (We need Global Admin or Power Platform admin role to enable it)
Once we have followed the above steps it adds the Copilot help pane in the Customer Service Hub app.
Similarly, for the Customer Service Workspace app, we can manage it in the corresponding Agent Experience profile.
Navigate to the Agent Experience >> Workspaces >> Manage (Agent Experience profiles)
We can see the Copilot AI features section (below is the out-the-box Customer Service workspace – default profile), we can accordingly update the corresponding agent experience profile(s) records configured/used for the agents.
Below we can see the Copilot help pane in the Customer Service workspace app.
Recently while trying to register the plugin, we got the below error
Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number).
It was because we were trying to register the assembly which was already registered in that environment, instead of updating it.
Let us see it in action, by creating a new journey record.
We get the option to select predefined examples to start with.
Here we have selected the last example “When a contact submits a marketing form, assign a phone call….”
On selecting it, we are presented with the option to specify the Trigger.
We have selected the existing Marketing Form Submitted trigger record here.
After specifying the trigger, we get the option to specify the marketing form or to leave it empty to run it for all the form submissions and also the audience type, which could be either Contact or Lead.
Clicking on Submit gives the option to review and then eventually Create Journey.
Clicking on Create Journey generates the journey for us.
We can review the journey, add any further content required, modify it, etc.
For example, we need to specify the follow-up email to be sent, before we can save and publish it.
Once we are done with defining the journey, we can publish it.
Nishant Rana's Weblog 