Skip to main content

Using Session Memory with CRM Portals

Recently while doing some client work, we noticed that CRM Portals does a post back when adding information within a sub-grid on an entity form.  Why is this an issue?  Because, if you have input fields on the form, these values are not written into  CRM till the save button at the bottom of the form is clicked.  So if a user inputs anything into the sub-grid after they fill in the fields, the post back action will remove what the user input.  This can make for a bad user experience.  To over come this, we can use session memory to temporarily store the values till the browsing session is ended.

To use session storage the first thing we will need to do is register onChange handlers to update the values the session memory when the user changes a value.  Here are some examples of onChange handlers written in JQuery:
1:  $(document).on('change', '#CHECKBOX ID', function () { SetSessionValue("#CHECKBOX ID") });  
2:  $(document).on('change keyup paste', '#TEXTBOX ID', function () { SetSessionValue("#TEXTBOX ID) });
#1 is for check boxes and picklists
#2 is for textbox inputs

The SetSessionValue is a reusable function I created to handle boolean, string and picklist.  Check my blog post on DateTime fields on how to handle onChange events with them.  Before we get into the source code for the SetSessionValue function, CRM Portals adds an _0 and _1 to the ID for boolean input on the portal.  That is why you see me add an _1 in the source code below:
1:  function SetSessionValue(fieldname) {  
2:    if ($(fieldname).hasClass('boolean-radio')) {  
3:      if ($(fieldname + "_1").is(':checked')) {  
4:        sessionStorage.setItem(fieldname, true);  
5:      }  
6:      else {  
7:        sessionStorage.setItem(fieldname, false);  
8:      }  
9:    }  
10:    else {  
11:      var fieldValue = null;  
12:      if ($(fieldname).hasClass('picklist')) {  
13:        fieldValue = $(fieldname).find(":selected").val();  
14:      }  
15:      else {  
16:        fieldValue = $(fieldname).val();  
17:      }  
18:      sessionStorage.setItem(fieldname, fieldValue);  
19:    }  
20:  }

To get the value out of session memory I created a small reusable function for that as well:
1:  function GetSessionValue(fieldname) {  
2:    var sessionValue = sessionStorage.getItem(fieldname);  
3:    return sessionValue;  
4:  }

Now with these parts we are writing and reading from session memory.  All  you need to do know is add a window.onload = function(){} or a $(document).ready to your code to populate your fields when a post back occurs.
Labels:

Comments

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...
100 comments
Read more

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 ...
23 comments
Read more

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.  ...
3 comments
Read more