Announcements
No record found.
Hi all,
How we can modify existing index in d365fo.
For example - Sales Table
Please give me more shed on this
Thanks!
Hi Arpan,
You cannot modify the existing index on standard tables.
There is no option to modify existing index event after extending the table.
Thanks,
Girish S.
Thanks Girish, then what the solution ? If required genuinely to modify index
From my understanding there is no other solution for this. Changing index through extension is not supported.
You have option to only create new indexes - Cannot modify existing index.
Creation of new index won't restrict the standard index fields - It will work along with standard index fields.
So, I don't think there is any other solution for this.
Can you tell me why you want to change the existing standard index?
Hi, It seems you have asked this question few years ago but I think it's still same behavior in F&O
community.dynamics.com/.../index-in-extension-table
It just query. Not required to change now. But if required, then what the solution. So, I am asking...
As I already said there is no other solution for this. If you change the index, then it will make the existing records collapsed, that's why its restricted.
Alternate will be adding validation while inserting records into the table via code.
The solution would be rethinking the solution direction. It was possible in AX2012 and before to do overlayering and change existing indexes. As mentioned, this is not possible. Suppose you need to move customizations from AX2009 or AX2012 to Dynamics 365 and the index was changed in the past, then you have to be creative and think of another solution for a business requirement.
An example I encountered myself before. The Form notes (FormLetterRemarks) got extended with more form note types (enumeration) and a business unit field which was also added to the primary key. Due to the business unit field as part of the primary key, it was not possible to do the same in Dynamics 365. This requirement was about having multiple notes on the invoices on different positions (top and bottom) which were different per business unit. In fact there was no need to have the details stored in the FormLetterRemarks table. We created a new table for the layout texts where we could manage to setup the same information and use it on invoice documents. The same requirement was fulfilled but implemented a bit different.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 659
André Arnaud de Cal... 465 Super User 2026 Season 1
Syed Haris Shah 304 Super User 2026 Season 1
