Is there another way to achieve a customer’s requirements without changing Microsoft Dynamics NAV standard table’s metadata? Yes!
Personally, I like to stay away from changing any standard table’s primary key, key, field type and length, why?
- Decreasing risk of introducing bugs
Recently, I was asked to modify the shipment agent table, as well as add a customer field to the table. The client wanted to be able to filter agent code based on the customer’s field.
Shipment agent tables primary key is code so adding the customer field without modifying primary key wouldn’t have given the client the solution they were looking for, and modifying the primary key has risk.
- Create a new table with agent code and customer code field.
- Add a new field to sales document table and page with a reference to the new table.
- Add code on-validate trigger of the new field and modify the standard agent code, based on the new field.
This option created a safer and upgrade friendly environment for our client.
If you have any questions, or want to learn more about how BDO IT Solutions can help implement Dynamics 365 Finance and Operations, Business Edition or Microsoft Dynamics NAV, please contact us.