{Power Integration}Email notification to all Queue Members on assigning a Case to Queue

Business requirement:

Email notification to be sent to all the Queue Members on assigning a Case to Queue.

Solution:

1. Add a step “When a row is added, modified or deleted” then rename it to “Trigger when a Queue item is created” and enter the following details:

Change Type: Added

Table Name: Queue Items

Scope: Organization

clip_image001

2. Add an action “Get a row by ID” and rename it as “GetCaseDetails” – This step is used to get a case record details:

Table Name: Cases

Row ID: Object (Value)

clip_image002

3. Add an action “Initialize Variable” and rename it to “Get all the emails of Queue Members” – This is used to store emails of all the queue members

Name: Queue Members Email

Type: String

clip_image004

4. Add an action “Initialize Variable” and rename it to “Record URL” – This is used to store the URL of Case record

Name: Case Record URL

Type: String

clip_image005

clip_image006

5. Add a condition to ensure when the type of record is case or not.

clip_image007

6. Under “Yes” part of a condition, add an action “List all records” and rename it to “List all members and their emails” – This is used to get all the users (Members) and their emails which we’ll use later. We may first need to fetch XML query.

Table Name: Users

Fetch XML Query:

<fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” distinct=”true”>

<entity name=”systemuser”>

<attribute name=”fullname” />

<attribute name=”systemuserid” />

<attribute name=”internalemailaddress” />

<order attribute=”fullname” descending=”false” />

<link-entity name=”queuemembership” from=”systemuserid” to=”systemuserid” visible=”false” intersect=”true”>

<link-entity name=”queue” from=”queueid” to=”queueid” alias=”ad”>

<filter type=”and”>

<condition attribute=”queueid” operator=”eq” uiname=”Queue Name” uitype=”queue” value=”{@{triggerOutputs()?[‘body/_queueid_value’]}}” />

</filter>

</link-entity>

</link-entity>

</entity>

</fetch>

clip_image009

7. Add an action “Apply to each” and select the “Value” which we are getting from previous step (List all Records) then add an action “Append to String Variable”

under Apply to each and enter following details:

Name: Select “Queue Member Email” variable

Value: Add following expression

concat(items(‘Apply_to_each’)?[‘internalemailaddress’],’;’)

clip_image011

8. Add an action “Send an email (V2)” and enter the required details:

To: Queue Members Email

clip_image013

9. Save the flow and test it.

clip_image015

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

image

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power Integration V3} Security sync between Dynamics 365 and SharePoint using Power Automate

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

image

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power Resolution} Solution import failure fix for Sales insights dependencies

Problem statement: In a recent project, we were evaluating Sales insights for the customer in Development environment. When we tried to move solution to QA for Sales development that was going on we faced an error in import:

clip_image002

Resolution steps:

Uninstall Sales insights from Dev environment by deleting the solutions in following order:

· SalesInsightsAddOn

· SalesInsightsMDLConfig

· msdyn_Conversationlntelligence

· msdyn_SalesRouting

· msdyn_segment

· msdyn_acceleratedsalessitemap

· msdyn_acceleratedsales

· msdyn_sequence

· msdynce_RelationshipAssistantAddOn

· msdyn_connectiongraph

· PredictiveLeadScoring

· PredictiveOpportunityScoring

· PredictiveForecast

· msdyn_PredictiveScoringCommon

· RelationshipAnalytics

At certain solutions you will get dependency issues, here is the resolution

For Sales Acceleration solution, we got below error:

clip_image004

Solution: Remove sequence control from Opportunity(form)

For Relationship analytics solution, we got below error:

clip_image006

Solution: Remove Action Cards control from Opportunity(form)

After following these steps, Sales insights components were able to be removed from the Development environment.

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

image

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power Integration} Create Teams meeting based on D365 CE Appointment

Business Requirement: Whenever Appointment is created in D365 CE, send Teams meeting invite to everyone and also update Team meeting URL back to the appointment.

Note: Server side sync is not enabled at the client tenant for Appointments.

Solution:

Step 1: Create an Automated cloud flow and set trigger as follows:

clip_image002

Step 2: Set the trigger condition as follows:

clip_image004

Step 3: Next step is very important; we need to route through all activity pointers to get email addressed of the attendees.

Filter to be used is _activityid_value eq

clip_image006

Step 4: Now we need to initialise variable to Append all List of Attendees:

clip_image008

Step 5: Loop through all returned Activity pointers and keep appending email address of the attendees into the string variable:

clip_image010

Step 6: Create Teams meeting as below. Note the formulas will need to be used to map start and end time.

formatDateTime(triggerOutputs()?[‘body/scheduledstart’],’yyyy-MM-dd HH:mm:ss’)

formatDateTime(triggerOutputs()?[‘body/scheduledend’],’yyyy-MM-dd HH:mm:ss’)

clip_image012

Step 7: update the appointment back with the Team meeting url by Updating the description:

concat(triggerOutputs()?[‘body/description’],’Click here for Team meeting url: ‘,outputs(‘Create_a_Teams_meeting’)?[‘body/onlineMeeting/joinUrl’])

clip_image013

Final Flow should look like this:

clip_image015

Result:

Now let us go and create appointment in D365:

clip_image017

Let us see the Teams calendar now:

clip_image019

Let us see Appointment description below in D365:

clip_image021

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

clip_image001[4]

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power Milestone}Half a million views and a Thank you note!

Thank you note for all the readers of CRM community and Microsoft, I crossed half a million views on my blog and was read in 191 countries in its journey so far.

image

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

clip_image001[4]

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power 2021} Trigger on save notification only when certain fields change in Model driven App

Business Requirement: Show notification in model driven form on save of table only when particular field/attribute has changed.

clip_image002

Solution: In Dynamics 365 , we can achieve this requirement using following script:

// function to show notitification on save
function onSave(executionContext) {
var formContext = executionContext.getFormContext();
var field = formContext.getAttribute(“fieldname”);
if (field.getValue() == VALUETOMATCH && field.getIsDirty())
{
var message = “Field name has changed”;
var messageString =
{
confirmButtonLabel: “Ok”,
text: message
};

var messageAlertOption =
{
height: 120,
width: 260
};

Xrm.Navigation.openAlertDialog(messageString, messageAlertOption);
}
}

Register this on save and show alerts based on field changed.

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

clip_image001[4]

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power 2021} Tips for Model driven form design

In today’s blog I will be covering some generic recommendations one should follow while designing Model driven forms.

clip_image001

Ø Review the fields on the form regularly

§ It happens across many CRM deployments over time that certain fields are removed due to business need or are no more relevant to a particular department (Role based forms). Please make sure to remove such unused fields from the form. The lesser the fields, the better the performance as lesser data needs to be transferred over the internet or intranet.

Ø Create different forms for different kinds of departments/ teams/ groups

§ Identify different departments or groupings of individuals in the organization

§ Track the fields that are more relevant to a grouping and consider creating different role based forms.

§ The approach will simplify the usage of form based on relevance to different users and also segregate security requirements.

Ø Avoid unsupported scripting

§ Anything that is not mentioned in Microsoft Docs will be considered an unsupported script. It might be an internal namespace library from Microsoft you are using or DOM manipulation.

§ Try to explain to the customer workarounds to use supported ways of using the form to achieve the requirement.

Ø Mobility considerations

§ If you have needs to use Mobile version of the D365 form, make sure you do proper previews while designing the form to get an idea of how it will appear in D365 Mobile App.

Ø Other Scripting considerations

§ Try to limit onload event handlers, this has a big impact on form load.

§ Use collapsed tabs wherever possible, for example in the case of web resource(html) inside the tab.

§ In case you need to show certain fields based on conditions, keep them initially hidden and then use script to enable them when condition is true.

§ Wherever possible use asynchronous requests instead of synchronous requests.

Ø Usage of sub-grids

§ Not all the sub-grids or related entity data needs to be visible at all times.

§ Try to use and recommend Related tab and Associated grids to the customer wherever related data is needed to be seen which is less frequent to be accessed.

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

clip_image001[4]

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to help, get in touch here: Click here

clip_image002[4]

{Power 2021} Prevent auto save on specific entities in Dynamics 365 CE

Business Requirement: Client wanted to disable auto save on certain Sales entities such as Leads and Opportunities so that it is sure that user has completed all the information. On all other entities, client requirement was to keep auto save.

Solution: We have to write a small client-side script and register it on save event of Lead and Opportunity record to achieve this requirement.

Here is the script:

function preventAutoSaveOperation(executionContext)

{

var eventArguments = executionContext.getEventArgs();

if (eventArguments.getSaveMode() == 70 || eventArguments.getSaveMode() == 2) {

eventArguments.preventDefault();

}

}

In case you are looking for different types that getSaveMode returns here is the complete list:

Value Save mode Table
1 Save All
2 Save and Close All
5 Deactivate All
6 Reactivate All
7 Send Email
15 Disqualify Lead
16 Qualify Lead
47 Assign User or Team owned tables
58 Save as Completed Activities
59 Save and New All
70 Auto Save All

Hope it helps and Power 365ing as usual!

Other ways to learn with me:

clip_image001[4]

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

I am here to help, get in touch here: Click here

clip_image002[4]