Skip to main content

AX 2012 R3 License types (CAL) for security roles

Below is the list of security roles and what license type they are.
Role License type
Accountant Enterprise Users
Accounting manager Enterprise Users
Accounting supervisor Enterprise Users
Accounts payable centralized payments clerk Enterprise Users
Accounts payable clerk Enterprise Users
Accounts payable manager Enterprise Users
Accounts payable payments clerk Enterprise Users
Accounts payable positive payment clerk Enterprise Users
Accounts receivable centralized payments clerk Enterprise Users
Accounts receivable clerk Enterprise Users
Accounts receivable manager Enterprise Users
Accounts receivable payments clerk Enterprise Users
Budget clerk Enterprise Users
Budget manager Enterprise Users
Buying agent Functional Users
Chief executive officer Enterprise Users
Chief financial officer Enterprise Users
Collections agent Enterprise Users
Collections manager Enterprise Users
Compensation and benefits manager Enterprise Users
Compliance manager Enterprise Users
Cost accountant Enterprise Users
Cost clerk Enterprise Users
Customer (external) Enterprise Users
Customer self-service administrator (external) Enterprise Users
Customer service manager Functional Users
Customer service representative Functional Users
Data import/export framework administrator Enterprise Users
Dispatcher Task Users
Employee Self Serve Users
Environmental clerk Functional Users
Environmental manager Functional Users
Field service technician Task Users
Financial controller Enterprise Users
Human resource assistant Functional Users
Human resource manager Enterprise Users
Information technology manager Enterprise Users
Logistics manager Functional Users
Machine operator Task Users
Manager Functional Users
Marketing coordinator Functional Users
Marketing manager Functional Users
Master data management Enterprise Users
Materials manager Enterprise Users
Payroll administrator Enterprise Users
Payroll manager Enterprise Users
Process engineer Enterprise Users
Process engineering manager Enterprise Users
Product design manager Enterprise Users
Product designer Enterprise Users
Production manager Enterprise Users
Production planner Enterprise Users
Production supervisor Enterprise Users
Project accountant Enterprise Users
Project assistant Functional Users
Project manager Functional Users
Project manager - Public Sector Functional Users
Project supervisor Enterprise Users
Project timesheet user Task Users
Purchasing agent Functional Users
Purchasing Agent - Public Sector Functional Users
Purchasing manager Enterprise Users
Quality control clerk Functional Users
Quality control manager Functional Users
Receiving clerk Task Users
Recruiter Functional Users
Retail catalog manager Functional Users
Retail merchandising manager Functional Users
Retail operations manager Functional Users
Retail store manager Functional Users
Retail warehouse clerk Functional Users
Sales clerk Functional Users
Sales manager Enterprise Users
Sales representative Functional Users
Security administrator Enterprise Users
Service delivery manager Functional Users
Shipping clerk Task Users
Shop supervisor Functional Users
Tax accountant Enterprise Users
Training manager Functional Users
Transportation coordinator Task Users
Treasurer Enterprise Users
Vendor (external) Enterprise Users
Vendor (external) - Public sector Enterprise Users
Vendor account manager Functional Users
Vendor portal administrator (external) Enterprise Users
Vendor portal administrator (external) - Public sector Enterprise Users
Vendor prospect (external) Functional Users
Warehouse manager Enterprise Users
Warehouse planner Functional Users
Warehouse worker Task Users
Waterspider Task Users
Click on this link to download an excel file that will allow you to drill down to each role and find out what menu items make up the license type.

UPDATED LINK (due to file size restrictions I zipped it up):

Below are some screenshots of what the file contains. A pivot table, the raw data and the list above.
Double click on the numbers in the pivot table and you will get a list of menu items that make it.
For details on how I got this data, see one of my earlier posts in 2012.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi