{"id":25596,"date":"2015-11-09T14:59:00","date_gmt":"2015-11-09T14:59:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/axsupport\/2015\/11\/09\/modifying-retail-pos-permissions-and-operations\/"},"modified":"2024-03-19T11:25:01","modified_gmt":"2024-03-19T18:25:01","slug":"modifying-retail-pos-permissions-and-operations","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/it-professional\/2015\/11\/09\/modifying-retail-pos-permissions-and-operations\/","title":{"rendered":"Modifying Retail POS permissions and operations"},"content":{"rendered":"
Applies to:\u00a0Microsoft Dynamics AX 2012 R3<\/p>\n
This article will explain how to link Operations with Permissions and Permissions groups as well as how to enable a Manager override prompt for certain operations.<\/p>\n
To get started, lets first define each of the 3 entities:<\/p>\n
HOW DO THEY RELATE<\/strong> On the Operations form you will notice that many of the Operations are listed with Permission ID’s of 0.\u00a0 This means that everyone has access to perform those functions.\u00a0 If you would like to limit these operations you can choose a Permission ID from the dropdown to associate it to a field on the Permission group form such as Manager Privileges.<\/p>\n The Permission ID and Permission ID2 fields allow you to assign two different Permissions to the operation.\u00a0 For example, we can set the 500-Void transaction Operation with a permission of 1001-allowTransactionVoiding as well as the 1002-managerPrivileges.\u00a0 This means 3 things:<\/p>\n The Operations form also has a Check user access field.\u00a0 This\u00a0determines if Retail POS should check a user’s privileges before the operation is performed. If this is not checked and you had Manager privileges set to an Operation, this will just skip the user validation and allow any user to perform the function.<\/p>\n MANAGER OVERRIDE PRIVILEGES<\/strong> You can also follow Shane’s blog below to add custom manager approvals:<\/p>\n Adding Manager Approval to Custom Operations<\/strong> OPERATIONS NOT LISTED ON THE PERMISSION GROUP FORM<\/strong> If you wanted to link additional Operations to the Permission group form, the out of the box solution would be to assign the Permissions in the Operations form to link it to an existing Permission Group field option.\u00a0 Let’s take the 1017-allowReturn permission and 114 Return transaction Operation.\u00a0 These are not available on the Permission group form.\u00a0\u00a0If you would like to toggle the access to this Operation, you could link this with another field such as “Allow transaction voiding”.\u00a0 So for Operation 114-Return transaction, assign Permission ID 1001.\u00a0 Now if a cashier’s Permission group has the “Allow transaction voiding” marked, they can also process Return transactions.<\/p>\n WORKER PERMISSIONS
\nOn the Permission group form, there is an option for “Allow create order”.\u00a0 When marked the cashier with this permission group can create customer orders at POS that also creates orders directly in AX. If we open the Operations form, you will see that Operation ID 620\u00a0is\u00a0for Create customer order and this has a Permission ID listed is 1020.\u00a0\u00a0Right click on 1020 and select View Details.\u00a0\u00a0This will open\u00a0the Permissions form and\u00a0you will see that 1020 relates to allowCreateOrder.\u00a0 If you look at the Operations list again, you will see that Operation 621-Create quotation also has Permission ID 1020 listed.\u00a0 What this means is when you place a checkmark next to the field “Allow create order” on the Permission group form, you also gain access to “Create quotation”.<\/p>\n<\/a><\/p>\n
\n
\nThe Manager privileges option can be confusing.\u00a0 A worker with Manager privileges should have access to all operations.\u00a0 Selecting Manger privileges on the Permission group form gives the user access to any Operation that is enabled on the form.\u00a0 Normally a manager would have most of the options marked on the Permission group form, thus giving them access to practically all functionality at the POS.\u00a0 Adding Manager Permission ID to any of the Operations will prompt a cashier who has Cashier permissions and doesn’t have direct permissions for a Manager login approval before continuing.<\/p>\n
\nhttp:\/\/blogs.msdn.com\/b\/axsupport\/archive\/2012\/08\/27\/ax-for-retail-2012-adding-manager-approval-to-custom-operations.aspx<\/p>\n
\nYou may have noticed that there are about 24 Permissions, but there are about 128 Operations.\u00a0\u00a0Many of these are left with\u00a0Permission ID’s of 0, meaning they are open for everyone to use.\u00a0 Keep in mind, as a cashier, I probably wouldn’t have access to edit the POS buttons available to me and thus would not have access to all of these\u00a0Operations such as\u00a0“Minimize POS” unless someone made that available.<\/p>\n
\n<\/strong>T<\/strong>he POS permission group is assigned to a worker at the Job level.\u00a0 To view this through Retail, go to: Retail >> Common >> Workers >> select a worker >> in the right pane, expand Position assignment and click on the hyperlink for the Job >> expand the Job classification fast tab >> view the POS permission group<\/p>\n