Dynamic CRM 2011/ CRM 2013 oData Error When Passing Dynamic Date as Parameter : Unrecognized 'Edm.DateTime' literal 'datetime'2014-05-12T04:5:28Z''

-


I face this error :
“Unrecognized 'Edm.DateTime' literal 'datetime'2014-05-12T04:5:28Z'' 

Resolution :
use a custome getODataUTCDateFilter() function:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
function getODataUTCDateFilter(date) {
    var monthString;
    var rawMonth = (date.getUTCMonth() + 1).toString();
    if (rawMonth.length == 1) {
        monthString = "0" + rawMonth;
    }
    else { monthString = rawMonth; }
 
    var dateString;
    var rawDate = date.getUTCDate().toString();
    if (rawDate.length == 1) {
        dateString = "0" + rawDate;
    }
    else { dateString = rawDate; }
 
    var hourString = date.getUTCHours().toString();
    if (hourString.length == 1)
        hourString = "0" + hourString;
 
    var minuteString = date.getUTCMinutes().toString();
    if (minuteString.length == 1)
        minuteString = "0" + minuteString;
 
    var secondString = date.getUTCSeconds().toString();
    if (secondString.length == 1)
        secondString = "0" + secondString;
 
    var DateFilter = "datetime'";
    DateFilter += date.getUTCFullYear() + "-";
    DateFilter += monthString + "-";
    DateFilter += dateString;
    DateFilter += "T" + hourString + ":";
    DateFilter += minuteString + ":";
    DateFilter += secondString + "Z'";
    return DateFilter;
}


Comments

Post a Comment

Popular posts from this blog

Ribbon Customization: Display Rules Based on Security Roles

-
Image
Some organizations need to allow certain users to access buttons on the Ribbon or Command Bar, while allowing others to utilize them based on the users’ security privileges. If you think this cannot be done, good news! It can! There are a few different ways to accomplish this functionality, and in today’s blog, we will show you how to solve your security role headaches. Let’s dive in! The steps outlined below require no coding and can be easily implemented utilizing the Ribbon Workbench and out-of-the-box security roles. To accomplish this, we created a custom entity (po_Security) to manage the display rules, however, this is  not  required as the exiting entities and privileges can be used. We created the new entity to ensure that no existing entity privileges were going to be effected, but the same principles will apply regardless if you chose to create a new entity or not. 1. First, start by downloading and installing the  Ribbon Workbench . 2. In CRM, create a...
Read more

Understanding Impersonation in Plugins and knowing when to use it

-
Image
Plugins are usually set to run as the calling user but sometimes you need to run a plugin with System User privileges. Before I explain how, we should first look at the why and how you impersonate users inside a plugin What is impersonation When you create a plugin in CRM  you write an execute method which gets passed in IServiceProvider serviceProvider This has lots of variables and objects such as IPluginExecutionContext ITracingService IOrganizationServiceFactory You use the IOrganisationServiceFactory to create a IOrganizationService.  The IOrganizationService is the CRM SDK, it provides you access to CRM programmatically .  CRM developers use the IOrganizationService (which I will often call CRMService) to CRUD operation – Create, Retrieve, Update, Delete records in CRM Assign records Change status pretty much everything you can do in CRM Here is the code to create the IOrganizationService, taken from the Plugin class of the C...
Read more

Real-Time Workflow vs Plugin: Execution Order

-
Image
Like plugins, real-time workflows are executed before (pre-operation) or after (post-operation) the core operation. Both are executed inside the same database transaction. Here are outlined some actions I have executed in order to evaluate their execution order: Customization of a custom entity named Entity A which contains two text fields named ‘Plugin Text’ and ‘Workflow Text’; Registration of two synchronous plugin steps for Pre Update and Post Update, which are triggered when the Entity A name field is updated: Pre Update Event: sets ‘Plugin Text’ with PLUGIN | PRE UPDATE; Post Update Event: sets ‘Plugin Text’ with PLUGIN | POST UPDATE; Creation of two real-time workflows; one runs before the update and the other runs after the update. Both are triggered when the Entity A name field is updated: Before Update: sets ‘Workflow Text’ with Workflow | PRE UPDATE; After Update: sets ‘Workflow Text’ with Workflow | POST UPDATE; Then after created and Entity A record, upd...
Read more