Custom data entity for good performance

(1) Share

Report

Posted on by CU10121822-0

506

Hi team,

As per the requirement, i suppose to develop custom data entity.

Before starting, i would like to think about the good performance in future thinking...

As per my knowledge, if I positively think about below things then I beleive , will not face performance on data entity:

1.We should avoid heavy code in data entity methods

Postload

InsertEntityToDataSource

MapEntityToDataSource

2. We should keep custom logic minimal

3. We should use computed or virtual columns only when it's really needed.

4. We should use batch jobs for large volume of data instead of interactive session.

5. We should use set based operation.

Pls validate is an i correct?

Let me know if anything needs to add.

Pls advise, thanks!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (2)

Sort by

Verified answer

Martin Dráb 239,992 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Yes, these points make sense, although how much business logic you need is driven by business requirements (and the data model); it's not your decision when building an entity.

Ideally, avoid postLoad()/virtual columns completely and use computed columns instead.

What you shouldn't forget about either are indexes.

Was this reply helpful? Yes No
Suggested answer

Subra 1,646 on at

Like (0)

Report
Copy link

Link copied!

Hi @CU10121822-0

Please find the below comments and let me know if you have any specific questions.

1. Yes, since those methods has been called frequently during import and export operations. so heavy processing can significantly impact performance.

2. Yes and Write only the logic required to meet the business requirement, and avoid unnecessary database calls or loops.

3. Only use either when a standard field or direct mapping cannot meet the requirement

4. Yes, Batch processing improves scalability and avoids user session timeouts.

5. Prefer statements such as update_recordset, insert_recordset, and delete_from where applicable.

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Verified answer

Anton Venter 20,825 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @CU10121822-0

Yes, your guidelines are correct and there is one more that I can add. For outbound data, simplify the query in your data entity as much as possible because the query plays a large role when it comes to performance on large datasets. Make your query lean by reducing the fields in the query so that only the fields that are actually used are selected in the query.

Edit:

In addition to the comments of the others.

Was this reply helpful? Yes No