18
A

ID's on features in Feature management

Anette Jansson on 9/30/2020 6:49:51 AM
We have a process to test and document the test of all new features. But features changes names from version to version, so it is difficult to keep track of them. I wish that a unique key should be added visually and searchable in the Feature management form.

One feature is called "@Tax:TaxCalculationOnInvoiceDateForVendInvoice" in version 10.0.13,
but in version 10.0.14 it is called "Sales tax rate on invoice date in vendor invoice journals". With a unique key it would be possible to know that they are the same feature, otherwise impossible.
Category: User Experience
STATUS DETAILS
Needs Votes

Comments

A

A

RE: ID's on features in Feature management

Tina van Heerden on 2/20/2025 10:40:08 AM

Identifying unique features is particularly challenging when the customers’ teams are looking at the features in different languages. Providing a unique id or even the recid will make feature comparison between environments possible.

Category: User Experience

A

A

RE: ID's on features in Feature management

Bertil Hökerberg on 9/30/2020 8:00:49 AM

Yes, this is a must for a robust feature management process. Also, Microsoft tells us that ALL features will be enforced enabled within a 12 month opt-in period after their availability. It is crucial for us to see that date on each and every feature so we can plan our test and enabling activities.

Category: User Experience