Refactorings I always do in JavaScript

by Sep 21, 2022

In the past 10 years I have updated a lot of JavaScript in Dynamics 365 CRM.

These are the 5 refactorings I always do:

✅ Adding executionContext to functions;
Passing the executionContext is the new way to access Xrm.Page. Make sure you flag ‘Pass execution context as first parameter’. Waiting patiently for Microsoft to make this the default 🥱.

✅ Replacing var with let or const;
Using let or const prevents stupid bugs where you re-declare or overwrite variables when you didn’t mean to.

✅ Better names for variables;
While I’m replacing var, I also improve the names of the variables to make it clear what their intension is.

✅ Invert if statements and use early returns;
Remove all those nested if statements and make your code clearer to understand by returning immediately when a condition doesn’t apply or inverting the check in a if statement.

✅ Use async/await;
Remove promises and .then methods that are nesting your code and replace it with the async/wait pattern to improve your code readability.

What are the refactorings you do when touching JavaScript code in Dynamics 365 CRM?

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more