Posts

Showing posts from May, 2018

Create a custom Grid in MS Dynamic CRM using Jquery DataTable

Image
Sometime we need to show our data in table format. We should use Jquery DataTable to show the data in sub-grid (Table) format.  Copy the below code and paste this code in your editor. And change the code as per your need. Here i will create a DataTable of Case Entity. <html> <head>     <title>MS Dynamic CRM</title>        <script src="ClientGlobalContext.js.aspx" type="text/javascript"></script>   <link rel="stylesheet" href="https://cdn.datatables.net/1.10.16/css/jquery.dataTables.min.css">  <link rel="stylesheet" href="https://cdn.datatables.net/select/1.2.5/css/select.dataTables.min.css">  <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">  <script src="https://code.jquery.com/jquery-1.12.4.js"> </script>  <script src="https://cdn.datatables.net/1.10.16/js/j

Asynchronous Processes/Wrokflows Stuck in InProgress/Waiting status in MS Dynamic CRM

Image
CRM developer/User once in a life faces the issue regarding Asynchronous Processes stuck in same status i.e. InPrgress/Waiting/Pausing/Canceling.You can see the system job status is not changing. The Reason- The main reason behind this issue  – Many jobs are in waiting status. Asyncoperationbase table become full due to many succeeded/canceled jobs occupied space. Asynchronous processes settings are not proper. The asynchronous workflows are not configured properly. Solution- The solution for this issue – Very first step is to restart the   Microsoft Dynamics CRM Asynchronous Processing Service.  This might work in many cases. Many Jobs are in waiting status-> you can update the job status to canceled and completed by creating console application or from database- a. Create the console and use the script – b. Using Database Query- Note- You should create restore(Checkpoint) point first before working on database directly to rollback changes if needed. You can

Bad Characters Messing Up Your Migration to Microsoft CRM Dynamics

Image
Our migration process typically consists of moving the source data into a staging SQL Server database prior to the actual migration to CRM. Among other reasons, this gives us a place to do data cleansing prior to the CRM migration. We run into many common issues such as field length differences and data type mismatches that are often found during the data mapping process with the customer. One less common issue we encounter in testing a migration is that some characters in the source data are not supported in CRM when importing data via the API. There are certain non-printable characters that are supported such as carriage-return and line-feed however others like record separator [char 30] or vertical tab [char 11] often are not accepted when migrating data to CRM. We've developed a common SQL framework we use to allow us to do some data analysis and clean-up of these invalid characters in our staging tables prior to doing our push of the data to CRM. In most cases we run th