Skip to main content

Security development tool [AX 2012]

There is a new tool released.

The Security Development Tool for Microsoft Dynamics AX 2012 is intended to help you more easily create and maintain security artefacts such as roles, duties, and privileges. The tool displays entry point permissions for a given role, duty, or privilege. Additional tools guide you through updates of the access levels for entry points. You can also use the tool to test a newly created or modified security role, duty, or privilege from the same interface, without using a different test user account. Additionally, you can use the tool to record business process flows and identify the entry points that are used.




How to install and how to use instructions are on technet
Download with the icon on the left and watch a 6 minute video on the right.


Key features:
  • Grant access via an entry point (easy as right click and grant access by adding to a duty)
  • Create a new privilege from the same view
  • Test the security by clicking open new workspace - it will simulate the role and allow you to test with your own account 
  • Record the entry points and will be presented on the form. Which you can then click and grant access.
  • View the effect on your license (Enterprise, functional etc). See what menu item has an effect on your license. See which configuration key is attached to what menu item. What layer it is in. Licensing is huge. As one menu item may change a user from a functional user to a enterprise user. License affect could be thousands of dollars.
Main thing you have to understand is modifying security roles from the front end will modify the AOT security element. It will sit in the layer you are in.
Lastly but not least, when installed from the model provided it will sit in your usr layer. It is pretty cool as it is self-contained and doesn’t overlap with the sys layer.


 Other links:



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.in(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