Custom API vs Custom Action vs Azure Function: Dataverse decision
The article discusses the decision-making process for choosing between Custom API, Custom Action, and Azure Function for a specific operation in Dataverse. Each option has distinct characteristics regarding latency, cost, and maintenance. The choice depends on the specific requirements of the operation and its integration with other services.
- ▪Custom Action is suitable for maintaining existing systems, while Custom API is preferred for new work due to better tooling.
- ▪Azure Function is ideal for operations that require external service calls or longer execution times.
- ▪Cost considerations generally favor Custom API for Dataverse-heavy tasks and Azure Function for those reliant on external dependencies.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3948393) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } SapotaCorp Posted on May 24 • Originally published at sapotacorp.vn on May 24 Custom API vs Custom Action vs Azure Function: Dataverse decision #powerplatform A client needs to expose a "calculate the loyalty rebate for this customer" operation. It reads three Dataverse tables, applies some business rules, writes a result. Every consumer - the Dynamics web app, a Power Automate flow, an external integration - should call the same operation. Three places we could put it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
