Skip to main content

Why do you need an inventory of Browsers? IE 11


As a developer you need to know which browsers are used by Dynamic 365 Users in your organization. The reason for this is quite simple, it will dictate your way of programming when it comes to scripting.

Most browsers majority of the time react the same way to JavaScript giving you a more predictable outcome, when it comes to IE 11 you have to be more careful, even though JavaScript has evolved since ECMAScript 5 IE 11 still using ECMAScript 5 and I am sure you have a handful of users that are on IE 11 in your organization.

ECMAScript 5 has so many limitation, yes you can use application like Babel to convert your code to ECMAScript 5 while coding with the latest version, if you have seen the output of Babel its not that palatable for my taste, it injects code to mitigate the shortcoming of ECMAScript 5, if you work with many developers I don’t think you are inclined to introduce a new process to generate your JavaScript files.

There are few things you can do
  1. Short term solution:- be mindful of IE 11 when you script, write on a version of JavaScript that is going to give you a predictable outcome in all of browsers, at the end of the day you have to deliver a product that is going to be successful and used by every user in your organization.
  2. Long Term solution:- Have a conversation with stakeholders, come up with a plan to transition to a better browser, Microsoft Edge, Chrome, Firefox and so on.



Thanks for reading.


Comments

Popular posts from this blog

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...

XMLHttpRequest vs Xrm.WebApi

  XMLHttpRequest vs Xrm.WebApi If you have written JavaScript code for Dynamics 365 you have seen the use of XMLHttpRequest or Xrm.WebApi to make server-side calls. The question is which one is the right one to use? So, let’s analyze the two types of calls. XMLHtttpRequest 1.        Synchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", false ); 2.        Asynchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", true ); So, passing true parameter is going to make asynchronous call while passing it false is going to make a Synchronous call. Xrm.WebApi 1.        Asynchronous a.        There is...