{"id":12461,"date":"2016-04-05T10:10:54","date_gmt":"2016-04-05T09:10:54","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/nav\/?p=12461"},"modified":"2024-03-05T12:02:16","modified_gmt":"2024-03-05T20:02:16","slug":"design-pattern-data-driven-blocked-entity","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2016\/04\/05\/design-pattern-data-driven-blocked-entity\/","title":{"rendered":"Design Pattern: Data-driven Blocked Entity"},"content":{"rendered":"
This pattern implements a generic mechanism for dynamically restricting and allowing usage of a record by the business process administrator.<\/p>\n
Problem<\/b><\/p>\n
A Dynamics NAV record can be used in a number of functionalities across the application. There are situations, however, when the administrator wants to restrict the consumption of such a record, as well as lift the restriction when it is no longer relevant.<\/p>\n
For example, a new customer record should not be used for posting documents until it is approved by the relevant approver.<\/p>\n