Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Rudy Salcedo]

We’ve been doing some analysis of our AX 2012 security roles via the Named user License Counts report.  One thing that we’re not clear about is what gives a security role an Access License Type of Enterprise, which is more expensive than Functional.

For example, 2 of the 3 custom roles below have an Enterprise access license type, and the 3rd has a Functional access license type.
         

Does anyone know what triggers AX to categorize a security role as Enterprise access license type?

——————————
Rudy Salcedo
Senior Programmer/Analyst
LaForce, Inc
Green Bay WI
——————————

[Mark Bailey]

Hi Rudy,

The main difference between functional and enterprise licenses are the duties & privileges that the user is allowed to carry out.

In your example the LF Sales Clerk & LF Processor roles are likely to have maintain/update privileges where the users have to post transactions in the system (E.g. Sales Order deliveries,returns, invoice generation etc..). This requires a functional license to carry out these tasks.

The other roles System user (std role) and LF Shopfloor personnel will only be read only or maybe only timesheet entry roles which only require an enterprise licenses.

Hope that helps to clarify.

Kind Regards

Mark

——————————
Mark Bailey
Application Consultant
Annata
Portsmouth
——————————
——————————————-

[Matt Pedersen]

If you are running AX2012 (which it looks like you are), I would highly suggest convincing one of your developers to install the Security Development Tool for you in a non-Production setting. This will allow you to see what privileges and duties are providing access to what and what level of licensing is associated with that duty or privilege. We are currently auditing our own. We are coming from only using out of the box roles to now giving access to only the duties and privileges needed. You would be surprised what is determined as Enterprise and what isn’t.

——————————
Matt Pedersen
Applied Medical Technology, Inc.
Brecksville OH
——————————
——————————————-

[Lizzeth Arredondo]

Hello Rudy, 

One of the main triggers to assign the Enterprise Licence Type are the functions of financial documents registration. E.g., if the role “LF Sales Clerk” is able to register the sales order invoice, it might be the reason for what the Enterprise Licence was assigned. Other examples could be: Posting a free text invoice, posting a customer payment journal, etc. Everything that affects Accounting in the system.

Every menu item in the system has a licence level that can’t be changed for natural functionality. Sometimes, just one menu item in a privilege make the licence higher, and maybe that menu item is not needed for the role. In these cases, it’s possible to reduce the licence level by customizing the privilege.

Best regards,

——————————
Lizzeth Arredondo
GCG – GONZALEZ, CORTINA, GLENDER Y CIA., S.A. DE C.V.
Col. Polanco Chapultepec
——————————
——————————————-

[Alex Meyer]

Rudy,

I have an entire blog series on user licensing in AX/D365FO, you can find the most applicable post here: https://alexdmeyer.com/2017/02/06/determining-user-licenses-in-dynamics-365-for-operations/

The basics are that each entry point (menu item) you assign to a role/duty/privilege has two parameters on it: ViewUserLicense and MaintainUserLicense if a user has read permission to that entry point then the license that is listed in the ViewUserLicense parameter is required. If that user has Update/Create/Delete to that menu item then the license in the MaintainUserLicense is required. Dynamics AX/365FO will then go through all of the accesses that a user is assigned from all of their roles and determine which license is required for the user based on their access to the menu items assigned.

Feel free to reach out with any more questions.

——————————
Alex Meyer
Director of Dynamics AX/365 for Finance & Operations Development
Fastpath
Des Moines, IA
——————————
——————————————-

[Rudy Salcedo]

Thanks for all the helpful info and advice everyone.  The Security Development Tool helped us pinpoint the specific menu items that are bumping some of our custom security roles to the Enterprise access license.

——————————
Rudy Salcedo
Senior Programmer/Analyst
LaForce, Inc
Green Bay WI
——————————
——————————————-