web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Finance | Project Operations, Human Resources, ... Data Entity - Where th...

Finance | Project Operations, Human Resources, ...

Answered

Data Entity - Where the business logics should reside

(0) Share

Report

Report

Posted on by Community Member

Hi When creating data entity, I am wondering where the business logic such as the following should be coded:

(1) Validation before the create/update/delete

(2) Populate some field dynamically based on the value of another field?

Should these business logic be coded at Entity or Table? What are Pros and Cons?

Thank you very much in advance!

I have the same question (0)

All responses Img

All responses (2)

Answers Img

Answers (2)

Verified answer

Mea_ 60,284 on at

Like (0)

Report

Code that should be executed for all sources (UI, x++, data migration, integration) should be done on a table level, if it is only UI then form level, if only data migration\integration - data entity.

Was this reply helpful? Yes No
Verified answer

Sukrut Parab 71,710 Moderator on at

Like (0)

Report

In addition you can also take a look at below docs link to now more about how to write validations table vs entity , where to default values etc.

docs.microsoft.com/.../validations-defaults-unmapped-fields

Was this reply helpful? Yes No

Join the conversation

Helpful resources

Quick Links

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1

Martin Dráb 664 Most Valuable Professional

#2

André Arnaud de Cal... 522 Super User 2025 Season 2

#3

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans