Update table index using table extension

(0) Share

Report

Posted on by maram fraij

I create a table extension to add extra fields to a standard table . I need to include these new fields in the index that is already created on the table with allow duplicate no , how can I update the index since I cannot add any fields also I cannot update index properties , is there any work around using table extension not customization ?

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (0)

Suggested answer

Martin Dráb 237,990 Most Valuable Professional on at

Like (1)

Report

Changing existing index isn't supported in extensions in the moment. You can create new indexes, though.

Was this reply helpful? Yes No
maram fraij on at

Like (0)

Report

how can I stop the effect of the already existing index ?

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

Like (0)

Report

Again, changing existing indexes through extensions is not supported.

Was this reply helpful? Yes No
Sheikh Sohail 6,125 on at

Like (0)

Report

This piece of code I found in MS hotfix...we need to test it before applying any where...
It seems during deployment & at db sync process it will be executed.

I will write the detail blog on this topic very soon

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

Like (0)

Report

Sohail, you can read about this framework in How to Write Data Upgrade Scripts for Microsoft Dynamics AX.

Was this reply helpful? Yes No
Sheikh Sohail 6,125 on at

Like (0)

Report

Martin, Thank you very much, will ping you for help if i stuck during implementation

Was this reply helpful? Yes No
JonathanDries 35 on at

Like (0)

Report

Hi, is there any update on this one?

Was this reply helpful? Yes No
nmaenpaa 101,162 Moderator on at

Like (0)

Report

I don't think this limitation on table extensions will be removed by Microsoft.

Changing standard unique indexes would potentially break every place in the system that trusts the original index definition (for example find and exist methods).

Was this reply helpful? Yes No
JonathanDries 35 on at

Like (0)

Report

I do understand the risk of willing to do this. But the way it is working now, it's impossible to extend the index with an extra extension field.

Now we've created a new index in the table extension, containing the original unique index fields and an extra field but this will never do the trick, unless the original index is changed to non-unique.

Our current workaround is to set the index uniqueness to false in the original table, and forcing the uniques through code (in the validateWrite method), wich can be overruled in extension package. But hereby we lose the possibility to use the original key as a replacement key so it's not ideal.

Was this reply helpful? Yes No
maram fraij on at

Like (0)

Report

Dear JonathanDries,

Regarding your workaround (Our current workaround is to set the index uniqueness to false in the original table) , how do you apply this since all index properties are not editable in table extension?

Was this reply helpful? Yes No