I spent last week or so discovering things on CRM 2013 tablet application and to be honest, it is pretty good. There are limitations but it is a good start for Dynamics CRM in tab and mobile market with having an out of box app.

Here are the series of blogs which pretty much sum all I could find on CRM 2013 Tablet application configuration, what can be done what cannot be done etc. For installation it is available in Google store for Android tabs, Windows store for Windows tabs and Apple store for IPAD tabs.

· Want to know how to configure multi entity search for CRM 2013 App. Here you go: Click here

· Want to know how to reconfigure IPAD app and options: Reconfigure vs Sign out for CRM 2013 App. Here you go: Click here

· Want to know Security Privileges required to access CRM 2013…

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?

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…