This job specifies the following information, The response that we get when we execute the request returns a Job Id of the Async Job created.
//get the Guid of the System Job created Guidjob Id=response.
You can also use the customization area in Dynamics 365 to define the behavior and format of the date and time attributes.
More information: Tech Net: Behavior and format of the Date and Time field property is available only if you are using Microsoft Dynamics CRM Online 2015 Update 1 or Microsoft Dynamics 365 (on-premises).
Go ahead and now change the behaviour of this field to “Date Only” Create a new Record Retrieve the value of this record and it would return it as “6/30/2015 AM”.
And in the database this field has been stored without the time component i.e setting the time as AM.
For the complete sample code, see Sample: Convert date and time behavior.
property to specify the date/time display format of the attribute irrespective of how it is stored in the system.
It appears that the UTC date/time is picked and the time part is being set as AM.
Suppose the user logged in has the Timezone specified as India Timezone.
This user entered a value in the date/time field prior to updating the field behaviour Now if we retrieve the value of the field Joining Date of the contact “Jim Glynn”, then we would get the Joining Date as “6/29/2015 PM” as we have specified the Behaviour for this field as User Local and User Local stores the UTC value.
After the execution and successful completion of the async job, if you now check the value of the existing data you will see it updated to appropriate date values based on the timezone provided.
No matter what is the timezone setup for the user that is viewing this record, the date would always show up as “6/30/2015”.