web

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

Dynamics 365 CommunityForums Finance | Project Operations, Human Resources, ... Best practice for upda...

Finance | Project Operations, Human Resources, ...

Suggested answer

Best practice for updating custom field on standard table (InventTable) during update

(0) Share

Report

Report

Posted on by harshil9898

71

Hello community,

I have a requirement on the standard InventTable where I added a custom field SyncStatus. The business rule is: whenever a record in InventTable is updated, this field should be set to Pending.

I see multiple possible ways to achieve this, and I’d like to understand which is the best practice from a performance and maintainability perspective:

Using the onUpdating table event handler
- Update SyncStatus = Pending in the handler before the update is committed.
Extending the update() method and setting the field before next update()

From my understanding:

Option 1 (onUpdating) seems to be the cleanest and most upgrade-friendly.
Option 2 also results in a single SQL update but directly extends the update() method.

Could you please confirm which approach is considered best practice in D365 F&O?
Also, are there specific scenarios where extending update() would still be recommended over using event handlers?

Thanks in advance for your insights!

[ExtensionOf(tableStr(InventTable))]
final class InventTable_Extension{
    public void update()
    {
        this.SyncStatus = SyncStatus::Pending;
        next update(); 
    }
}

Categories:

Dynamics 365 Finance

Microsoft Dynamics AX

I have the same question (0)

All responses Img

All responses (1)

Answers Img

Answers (0)

Suggested answer

André Arnaud de Cal... 297,902 Super User 2025 Season 2 on at

Like (1)

Report

Best practice for updating custom field on standard table (InventTable) during update

Hi harshil9898,

Both options mentioned by you are extending the application. There is no difference in upgrade-friendly. The first one is using data events, the second one Chain of Command. Choosing between these two, my preference is CoC (option 2).

However, maintaining the field for sync purposes is not required. For BYOD synchronization, Microsoft relies on SQL server capabilities: change tracking. These can be created and read by a custom integration job as well.

Also, the Dataverse connector (using F&O virtual entities) can be used as a trigger for changes and then start sending over data from one to another application using e.g. Logic Apps or Power Automate.

Was this reply helpful? Yes No

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Our Community Code of Conduct has been updated!

Quick Links

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

#1

Sohaib Cheema 814 User Group Leader

#2

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

#3

CA Neeraj Kumar 622

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans