Javascript async/await in Dynamics 365

by Sep 14, 2022

Why isn’t targeting ES5 in JavaScript working anymore in Dynamics 365 / Power Platform.

I see a lot of Dynamics 365 still targeting ES5 (or ES6) in JavaScript and missing out on some new features. Looking at the features in JavaScript and their support in browsers we can safely choose for ES2017 now a days.

Why ES2017? You can use async/await!

This is such a big win, because:
✅ No more callbacks and promises
✅ Enforces function to always returns a promise, so you can’t forget
✅ More concise, no more nesting callbacks: callback hell.
✅ Reads top down
✅ Handle errors via try/catch

But you use transpiling with TypeScript and/or Babel?

Even when transpiling code, it looks more like the original code, instead of gibberish. This will help in understanding the code in production when you need to fix a bug ASAP.

Dare I say it? Target ES2020!

Looking at how browsers auto-update now a days, you can even target ES2020! This will bring the feature of ?. and ?? operators which help even more in writing clean code. This feature is available in browsers from the beginning of 2020.

Are you going to switch?

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