Skip to main content

CRM Portals OnChange Event For DateTime

Occasionally when working with CRM Portals you may run into the need to get the OnChange event for a date time field.  Because of the way that CRM Portals renders date time fields this is slightly more complicated then working with text boxes, check boxes and pick lists.  During my process I ended up reaching out to Microsoft for help on this and below are the steps they provided to help me with this problem:

1) Click on the date time control
2) Press F12
3) In console type $('div.control') and hit enter (this will give you a list of div controls)
4) Locate the div control for the date time field
5) Go to the entity form or web page in CRM and add the following code snippet (replace the 2 with the number your div control is located at):

1:      $(document).ready(function ()  
2:      {  
3:        var dpcontrol = $('div.control')[2];  
4:        $(dpcontrol).on("dp.change", function (e)   
5:        {  
6:           alert("On change Event Triggered");  
7:           alert(e.date);  
8:        });  
9:      });  

Change the 2 alerts to whatever you need to happen during the OnChange event.

Comments

  1. Nice. Even better would be to use:
    var dpcontrol = $("#id_of_your_field").closest("div.control");

    Great post!

    ReplyDelete
  2. Many companies use a crm free download system, and all companies could benefit from using one. But how many people understand the implications of installing CRM? To help you make the right decision in choosing a CRM system, I've answered some of the most common CRM-related questions.

    ReplyDelete
  3. This is ridiculous! I have gone on this site several times, trying to put the codes in, but whoever made this game is making sure no one wins. Virtual Event Companies

    ReplyDelete
  4. Thank you so much for sharing this worth able content with us. The concept taken here will be useful for my future programs and i will surely implement them in my study. Keep blogging article like this.
    Project Management

    ReplyDelete
  5. I located one reliable example of this fact through this blog website. I am mosting likely to use such information now.
    CRM Support

    ReplyDelete
  6. Great article by the great author, it is very massive and informative but still preaches the way to sounds like that it has some beautiful thoughts described so I really appreciate this article. Best What is CRM service provider.

    ReplyDelete
  7. I read a article under the same title some time ago, but this articles quality is much, much better. How you do this.. Shisha Hire

    ReplyDelete
  8. This is important information which is shared by you. This info is meaningful and important for everyone to increase our knowledge about it. Always keep sharing this kind of information. Thank you. Read more info about Hybrid Event Promotion

    ReplyDelete
  9. You have a genuine capacity to compose a substance that is useful for us. You have shared an amazing post about Virtual Conference Platform.Much obliged to you for your endeavors in sharing such information with us.

    ReplyDelete
  10. Choosing a CRM solution that is functional as well as cost effective can be very challenging especially if you are on the lookout for small business CRM solutions. advantages and disadvantages of CRM

    ReplyDelete
  11. Hi
    only one issue with Datepicker is when we select the same date the event is not triggering.
    For example, if you select 16th and then selects the same date againthen the on change event is not triggering.
    Thanks
    CG

    ReplyDelete

Post a Comment

Popular posts from this blog

Power Pages Update Last Successful Login Using JavaScript and Power Pages API

 Recently while working on a Power Pages implementation for a client, I had the requirement to show the last time a user logged in on their profile page.  I thought this would be easy to do as there is already a field on the contact record for "Last Successful Login" (      adx_identity_lastsuccessfullogin).  This use to update when a user logged in, but it appears Microsoft has removed that automation. While searching I came across a few different ways of achieving this task.  One used application insights in Azure and another one used an HTTP endpoint setup in Power Automate.  I thought, this needs to be simpler.  What I came up with is to use Liquid with JavaScript to tell if a user is logged in or not.  Then use the new Power Pages api to update the logged in users contact record to mark the last time they logged in. Here is the approach I setup: 1) Make sure you turn on the api for contact in Site Settings. 1) Link to Microsoft Do...

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if ...

Lookup In Select of URL For Power Pages

 While working on a Power Pages implementation I was consume the Power Pages API to get a Lookup table so I could show and hide information on the form using jQuery.  One issue I was having is I couldn't get a lookup field to return even though I had it as a field in the site setting for the table and included it in the my select statement in the URL.  I kept getting an `unexpected error occurred`. This issue is caused because lookup's are made up using 3 fields. 1) Formatted Value = The information you see in the lookup field (i.e. the record name) 2) Logical Name = The table the related record is a part of 3) Id = The id of the related record In the api there is a 4th field that is returned that is the Associated Navigation Property and it is the logical name of the lookup field. When setting up our select and even saying what columns can be returned in the API, we have to think how the OData endpoint will return the data to us.  ...