New fields are often needed in a master data table. This could be, for example, an alternative item number in the item master. Until now, new fields…
New fields are often needed in a master data table. This could be, for example, an alternative item number in the item master. Until now, new fields always had to be created by a developer in the database and released into the production system via the UAT system (User Acceptance Test). A complete release process for a single field. With the latest version of Dynamics 365 for Finance and Operations, a user with the appropriate role can add new fields at runtime: Via personalisation, you can display additional fields as before and, as a new option, create new fields A dialog guides the user through the creation. In this way, number, text, date, selection fields (lookup) or checkboxes can be created. Translations can be maintained in a central administration Export and import via Excel is possible Fields appear in the database log As practical as the function is, there are some notable limitations for such customer-specific fields: No index in the database. Searching and filtering in these fields is possible, but not optimised. The new field does not automatically appear for all other users. Manual adding or distribution of the personalisation is required. Not possible on all tables. For example, not possible on transaction tables (journal lines). Microsoft recommends no more than 20 fields per table Further information from Microsoft: Adding custom fields in Dynamics 365 for Finance and Operations (Youtube) Post on Microsoft Docs