As part of the upcoming license enforcement for Microsoft Dynamics 365 F&O, the license calculation logic was completely rebuilt and now executed outside of the application. The results are brought back in new licensing-related tables. The legacy calculation logic has been deprecated, and where the outcome was used, the fields showing a particular license were removed. When the View permission page showed the license levels in the past, it was easy to find which privileges and duties as part of a security role were causing a higher license requirement than intended. Today, you can relatively easily find the securable objects that can be removed or set as read-only to lower the license requirement for a security role, but then there is no drill-down to find the related privileges and duties. In this post, I will share a trick to make you more productive.
Read more