Category: CRM

Business Hours in Service Level Agreements (SLA) in CRM 2013


Hi,

Was looking into how the business hours works in SLA.

For this we a created new SLA record on CreatedOn field and which will update one of the fields on warning after one minute and some other field on failure after waiting for 5 minute.

And Applicable When -> when the Title field of Case contains “mm” text in it.

 


Following was the schedule

We created case record that satisfies the above condition at 3:28 P.M.

It updated one field on warning after one minute and then on 3:30 it went into wait condition and then resumed at 3:40 and showed failure at 3:43 as expected (i.e. total 5 minutes).

So it did consider the Break specified and on resuming ran for the remaining 3 minutes.

Hope it helps..

 

 

 

 

 

 


Got 2 million views (hits) on my blog


Happy to reach this milestone today – (24 September 2014)

 

New in CRM Online Spring ‘14 / Service Pack 1 / Leo: SLAs


CRM 2013 Service Pack 1: Entitlements, SLAs and That Loveeeely Timer Control


dynamicscrmgirl's avatardynamicscrmgirl

CRM 2013 Service Pack 1 has introduced Enterprise Case Management functionalities, which includes new service entities such as “Entitlement” and “SLA”, and that lovely time control on case forms.

How do I put everything together?

View original post 661 more words

CRM 2011 Context Depth Issue


https://community.dynamics.com/crm/b/magnetismsolutionscrmblog/archive/2013/04/28/crm-2011-plugins-avoiding-infinite-loops.aspx

Danny Varghese's avatarDanny Varghese's Blog

With CRM 2011 events now being transactional, i.e. when an error occurs, the requested change is rolled back, this has posed its own unique set of problems.  Here’s one I faced recently…

Background Information:

Let’s say a user enters information on a form on any entity and clicks save.  Like any other .NET web application, the data entered by the user is then submitted to the database.  Validation occurs, and if valid, the data is submitted and then finally committed to the database.  The resulting values (including any calculations done by CRM plug-ins) are returned back to the form for the user to see.

In CRM 4.0, all the values entered on a form are submitted to the database as a collection of properties (field names and values).  If any validation errors occurs, the collection of properties containing the values the user entered is NOT submitted, but rather the collection…

View original post 382 more words

Fixed – Unhandled Exception: Microsoft.Crm.CrmException: Cannot create a lookup without the required parameters in CRM 2013


Hi,

Got this error in one of the steps in the Action. It was updating one of the lookup field using Update step.

The issue was that the lookup field was not in the form. Adding that particular field in the form back resolved the issue.

Hope this helps..