Dynamics 365 Finance
Category
Nov 11, 2023
Published date
Text
Article Type
AI Summary
- The article discusses a hidden feature flag that has changed how user licensing is performed in Dynamics 365 Finance and Operations (D365FO).
- The author shares a scenario where a specific privilege is reported as requiring a 'Team Member' license in the 'View Permissions' report, but the code in the application suggests that an 'Enterprise/Operations' level license is required.
- The author conducts a technical deep dive into the code and discovers that the license calculation is performed by an external DLL called Microsoft.Dynamics.AX.Security.Management.UI. The license calculation is handled by the RelatedObjectDataLicenseProcessor, LicenseProcessor, and MenuItemLicenseProperties classes.
- The root cause of the licensing discrepancy is found in the ComputeForGrant method of the MenuItemLicenseProperties class. If the access granted to the menu item is at a 'Read' level and the feature flight 'DisabledReadGrantTeamMembersLicense' is disabled, the ViewUserLicense parameter is overridden to be a 'Team Member' license. Otherwise, the original ViewUserLicense parameter is returned.
- The author notes that the change in the licensing logic occurred between versions 10.0.32 and 10.0.35 of D365FO.
- The article highlights that the licensing change impacts over 680 menu items that have the ViewUserLicense set to either 'Activity' or 'Operations' level license.
- The author mentions that they were unable to find any mention of this licensing change in the recent release notes from Microsoft.
- The author concludes that Microsoft expects this new licensing logic to be part of the default methodology going forward.
Registered users can view the full text for FREE!
Sign In Now!