Microsoft Dynamics CRM – Page 32 – Nishant Rana's Weblog

A security error has occurred. Make sure you are signed into Microsoft Dynamics CRM and try again in Click Dimensions.

We had this issue in past when we started getting below error in most of the entities of Click Dimensions.

The issue can occur if the password would have expired or changed for the Service Credentials account of Click Dimensions.

Go to Settings à ClickDimensions Settings à Service Credentials.

In our case it wasn’t changed but we were still getting the issue. The only way we were able to fix it was to specify a different account for the Service Credentials.

Hope it helps.

The remote server returned an error: (403) Forbidden while sending SMS from Click Dimension

We got the below while sending SMS from Click Dimension. We were using Bulk SMS as our SMS connector for Click Dimension.

When we opened the Text Messages record we figured out that we were getting “The remove serve returned an error (403) Forbidden.

This occurred because we had our credit with Bulk SMS already consumed.

The issue got fixed when bought the credits again with Bulk SMS.

https://youtu.be/d__-flPGoFc

Hope it helps.

How to – Convert Fetch XML to SQL in Dynamics 365

Hi,

Recently we had a requirement to convert Fetch XML query of certain views to SQL. Basically, we wanted to validate it again the source DB from which we push the data inside Dynamics 365.

For this we can use the below managed solution,

https://fetchxml2sql.codeplex.com/

The tool is built using Silverlight so will only work in IE.

The other tool is that we can use is one of the most useful plugins – Fetch XML Builder of XRM Tool Box.

Below video explains how to use them

https://www.youtube.com/watch?v=OESJxa3bwrU

And in case you’d feel like converting fetch xml to SQL we have

http://www.sql2fetchxml.com/

Hope it helps..

Plugin on AddListMembers message. When does it fire?

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.

Dynamics Marketing List – The plugin didn’t trigger.
Static Marketing List – The plugin didn’t trigger for “Add using Lookup“. It only triggered for “Add using Advanced Find” when “Add only the selected members to the marketing list” option was selected. It didn’t trigger for “Add all the members returned by the search to the marketing list“

This slideshow requires JavaScript.

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

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,

Select the new KPI created.
Specify Applicable as when status reason not equal to either completed or cancelled.
Failure after 18 hours i.e. 2 Days (as we specified 9 hours working in Customer Service Schedule)
Warning as 9 hours.

Activate and Set as Default.

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 22^nd Nov 8 A.M. and we can see the resolve by date to be 27^th.

In our SLA we had set the Failure After as 18 hours, and the holiday was set on 23^rd and 24^th. And also 25^th and 26^th being Sat-Sun the Failure Time comes as 27^th Monday, which is exactly what we want.

Another interesting way of implementing the same without using SLA.

https://community.dynamics.com/crm/b/hayersdynamicscrm/archive/2014/06/20/dynamics-crm-how-to-add-working-days-by-calculating-business-closure-and-weekends

Hope it helps..