Help Understanding Customization in Dynamics 365 Sales vs Business Central (as a Developer)

(2) Share

Report

Posted on by CU24061739-0

I come from a Business Central background where I’ve worked on customizations using both AL (in Visual Studio Code) and previously with C/AL in NAV. In BC, I’m used to writing code to create custom pages, add buttons with logic, define new tables and fields, and use codeunits with exposed methods for integration. All of which requires writing proper AL code.

Now I’m starting to explore Dynamics 365 Sales (Sales Hub), which I understand is a model-driven app that runs on the Power Platform and uses Dataverse to store the (shared) data. It seems like you can do a lot from the browser UI of power apps. For example, creating tables, forms, and even adding buttons to the ribbon all without writing code.

I’m curious to understand:

What kind of customizations can be done directly in the browser with no code (like drag-and-drop)?
What kind of things require low-code scripting, and what scripting language is used? Like adding some logic behind a button.
In which cases would I need a developer/programmer? For example, are things like data validation, integration, or automation possible without a developer?
Can I write custom methods that perform complex logic (like reading/writing from multiple tables, deleting records, applying business rules, etc.) and then expose them as a simple HTTP API to be called from outside or as a button on a page? Or is this something that needs to be done differently in the Dataverse/Power Platform world?

Would really appreciate if someone could help clarify this or point me to some resources specifically meant for developers and customizations. I'm trying to wrap my head around the different terminology and construct a learning path (so please mention whatever you think I should know). Googling has brought up things like XrmToolBox, Plugins, JavaScript, and Power Automate, but I’m not sure when each of these is used, and whether they are still relevant or commonly used today.

Thanks!

Categories:

Dynamics 365 Sales

I have the same question (0)

All responses (3)

Answers (1)

CU24061739-0 10 on at

Like (1)

Report

Help Understanding Customization in Dynamics 365 Sales vs Business Central (as a Developer)

Thanks @Gerardo Rentería García

But i dont see anything about XrmToolBox and Plugins on there.

Sales

https://learn.microsoft.com/en-us/dynamics365/sales/developer/developer-guide?wt.mc_id=MVP_354389

Dataverse

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/overview

Model Driven Apps

https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/overview

Was this reply helpful? Yes No
Verified answer

Gerardo Rentería Ga... 23,431 Most Valuable Professional on at

Like (1)

Report

Help Understanding Customization in Dynamics 365 Sales vs Business Central (as a Developer)

Hi, good day
I hope this can help you, and give you some hints.

Developer Guide | Microsoft Learn

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Muhammad Shahzad Sh... 2,331 Most Valuable Professional on at

Like (0)

Report
Help Understanding Customization in Dynamics 365 Sales vs Business Central (as a Developer)

1. No-Code Customizations

Create/modify Tables (entities), Fields, Forms, Views, Dashboards

Add Business Rules (for basic logic/validation)

Customize the Command Bar (Ribbon) using Power Fx and Command Designer

Configure Model-Driven Apps (like Sales Hub)

Set up Security Roles, Business Units, Teams

Build simple Power Automate flows

2. Low-Code Customizations

JavaScript (Client-side logic): e.g., on form load/change/save to validate fields, show/hide sections

Power Automate: For process automation, integrations (HTTP, approvals, emails, data sync)

Power Fx: Used in Canvas apps and newer command bar buttons

Calculated & Rollup Fields: No-code but formula-based logic

3. Developer/Pro-Code Scenarios

Plugins (C#): Server-side logic (e.g., pre/post operation validation, cascade updates)

Custom APIs/Code Activities: Complex business logic exposed via HTTP or used in Power Automate

Custom Connectors: For external API integration

PCF Controls: Custom visual UI components

Web Resources: HTML, JS, CSS files for custom interfaces

Azure Functions or Logic Apps: Heavy integrations or background processing

Was this reply helpful? Yes No

Community site session details

Help Understanding Customization in Dynamics 365 Sales vs Business Central (as a Developer)

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Andrés Arias – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

Help Understanding Customization in Dynamics 365 Sales vs Business Central (as a Developer)

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Andrés Arias – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates