Packt’s $5 sale is now on! Grab my @packtpub book Dynamics 365 Application Development for just $5 https://www.packtpub.com/application-development/dynamics-365-application-development.

Packt’s $5 sale is now on! Grab my @packtpub book Dynamics 365 Application Development for just $5 https://www.packtpub.com/application-development/dynamics-365-application-development.

Helpful article helped us fixed an issue on USD 3.0
Hello friends, recently I migrated my configurations from USD 2 to USD3. After successful migration I added one action call to scan for data parameters on save event oh hosted control. I created few new hosted control of same type and there save even was working as expected.
Issue: save event was not triggering for CRM Page type hosted control.
Reason: after scratching my head around this issue for i long i thought of comparing this hosted control with other hosted control when save even was working. I create a advance find and added all fields of hosted control entity and added filter to only display details of these 2 hosted controld

When i was comparing the fields values for both hosted control I found one difference in…
View original post 80 more words
In one of our recent implementations involving marketing list entity, we were analysing the AddListMembers message for it.
We registered a plugin on AddListMembers message and below were our findings.


So basically, we need to be very careful while implementing a plugin on AddListMembers message.
Hope it helps..
Auto-Closure of Task considering Work Hours and Holidays in Dynamics 365.
Recently we had a requirement to auto close the task after 2 days of due date passed. Here we had to consider work hours and holidays as well.
The good thing was that with SLA considering both work hours and holidays, we could implement this without writing a single piece of code.
Below are the steps to implement it –
Enable SLA for Task

Navigate to Settings à Service Management à Click on Service Level Agreement and create a new SLA against Task.

Create a new SLA record with following details.

Here we need to specify Business Hours in our SLA. For this, we will be creating a Customer Service Schedule record which observes the holiday.
So let us first define a new Holiday Schedule.
Navigate to Settings à Service Management and click on Holiday Schedule.
This holiday schedule will be used while defining Customer Service Schedule.

Create a holiday schedule record and add holiday records to it.

Here we have added a sample holiday of 2 days.

Now let us define the Business Hours.
Navigate to Settings à Service Management à Customer Service Schedule

Create a new schedule

Set Workdays as Mon – Friday and work hours as 8 – 5 P.M. and select our Holiday Schedule record created earlier.

Let us update our SLA record with these new customer service schedule.

Let us try creating a new SLA Item record. Here we will find that there is no KPI’s defined i.e. SLA KPI drop down doesn’t have any value.

Let us define an SLA KPI here.
For defining KPI we need to create a new relationship between Task and SLA KPI Instance (n-1 i.e. Many to 1).

Open the Task form for customization and add this new lookup SLA KPI Instance on the form.
Next, add a Quick View Form of SLA KPI entity in it.

Click on Edit to update the Resolve By SLA quick view form to add a new field Failure Time in it.

Add the Quick View Form to the Task form.

Back in our SLA item,


Creating a task with Due Date will start the Timer for Resolve In.

In the task record created we have set the Due Date to 22nd Nov 8 A.M. and we can see the resolve by date to be 27th.
In our SLA we had set the Failure After as 18 hours, and the holiday was set on 23rd and 24th. And also 25th and 26th being Sat-Sun the Failure Time comes as 27th Monday, which is exactly what we want.
Another interesting way of implementing the same without using SLA.
Hope it helps..
Recently while opening a marketing list record inside Dynamics 365, we got the below issue.


The issue was because we had multiple marketing list forms and the one the user had accessed last had all the security roles removed from it.
Enabling the security role that user had, for that particular form fixed the issue.

Hope it helps..
In Dynamics 365, we can now define Session timeout and Inactivity timeout.
We need to go Settings à Administration à System Settings à General Tab

By default, the session timeout is set to 24 hours along with 20 minutes for warning the user.
We can set our custom values there.
| Enter maximum session length | 60 – 1440 minutes. ( 1 to 24 hour) |
| How long before the session expires do you want to show a timeout warning? | 20 – 1440 minutes. Must be less than maximum session length. |
We can also set the timeout based on inactivity. By default, this setting is not enabled. Below are the values that we can set for inactivity timeout.
| Enable session timeout due to inactivity | 5 – 1440 minutes. (5 minutes to 24 hours) – Must be less than the maximum session length. |
| How long before the session expires do you want to show an inactivity warning? | Less than Session timeout due to inactivity |
Session Timeout warning à

Session expired à

Inactivity warning à

Inactivity Session expiration à

More details.
https://docs.microsoft.com/en-in/dynamics365/customer-engagement/admin/user-session-management
Hope it helps..