Table extension in AX 2012

(0) Share

Report

Posted on by Community Member

Dear All,

I have a doubt in extending a table from Standard table (HcmWorker). Earlier, I had added new fields in Hcmworker table. But now, I want to move the customizations to a new customized table. For table inheritance, SupportInheritance property should be set to Yes. But Hcmworker table doesn't have it. I referred the link http://daxonline.org/9-table-extension-framework.html. But it also requires a delete action to be created in standard table & I don't need it. Is there anyother way to extend a new table from Hcmworker?

Thanks in advance!!

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi YellowRose,

Why do you want to move the fields to another table? What type of fields did you use? This would help us understanding your situation and suggest to leave the fields in the current table (is also in a way an extension) or create a new table where the HcmWorker RecordId has a one-on-one reference.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Dear André,

Thanks for your prompt reply!! I am segregating the customizations done on Standard table to customized tables, so that it would be easy while doing migration in future.

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

As new fields are stored in the model as delta on the table, it is already separated from the standard. When you move models, the fields are extensions, not overlayering standard objects. If you have changes on standard methods, like insert and update, you could consider using pre-or post events. If you didn't change indexes, the upgrade would be easier as well.

Was this reply helpful? Yes No
Verified answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Microsoft's recommendation is not to have more than 50 fields on a standard table, so separating your custom fields is always a good idea.

https://blogs.msdn.microsoft.com/axinthefield/top-10-issues-discovered-from-dynamics-ax-code-review/

My rule of thumb is to create a new table for customizations which have more 5 new fields on standard tables, and even a separate table if you are planning to have Memo/container/very large string fields.

However, you are mixing up SC/sc (subclass-superclass) type extensions on the AX tables (inheritance) with what you want to achieve.

You simply have to create your new table, then in Relations add your relation to the parent table first like HCMWorker. After that create a new primary key-based relationship, which will add a RecId field and reference for you automatically in majority of the cases.

Then you have to ensure that if the parent record is created, you insert the row in your corresponding custom table, especially if you inner join it on the forms where it is being used.

Was this reply helpful? Yes No
Martin Dráb 237,801 Most Valuable Professional on at

Like (0)

Report

@YellowRose: How you can say that you don't any delete action when using the table extension framework? If you extend a worker with ten fields (kept in your separate table) and somebody deletes the worker, why would you keep those ten fields of a non-existing worker? The delete action is necessary to keep your database in a consistent state.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi, See if this helps: www.intech-systems.com/table-extension-framework-dynamics-ax

Was this reply helpful? Yes No