Dynamics NAVAX

I was recently looking at different ways of analyzing the security in the AOT. I found an Addin that is in Visual Studio. Click on the “View related objects and licenses for all roles”. It takes about 5 minutes to put all the data together and export an Excel file. You get two worksheets. License information – Shows the different security objects; Roles, Duties and Privileges. Showing the license type. View related objects – This is a detailed exploded view of the Roles, duties, privileges, resource (I.e. menu item) Based on the second tab I was able to create a pivot table. This allows me to figure out what makes a particular license Enterprise. The thing you have to keep in mind is that this is looking at the AOT. If you have made security changes in the front end, this Addin won’t recognize it. If you want to review security from the front end then navigation to the Security configuration form. Then click on the View permissions. You will get a similar list as the Ex...

I will start backward. Show what the result is and then will go into what I did to achieve this. Lets say you want to filter the customer records based on the department dimensions that are assigned to the user logged in. This might include restricting the sales orders too based on those customers. Result Setup Create a new Organization hierarchy with the Security purpose assigned. Edit the hierarchy and add the departments you plan on using. Create a new security role and assigned organizations by specifically granting access to the departments. Technical Now for the technical aspects of this. I used security policies to achieve this result. xds temp table which I have a the code to build (explode) the departments into the temp table. Query which joins the customer table to the dimension tables so we can specifically get the Department dimension Class created a method to retrieve the Department dimension attribute recId New role which is a main driver of the roles...

There is enough detail on msdn regarding this topic. But what I wanted to make clear is what actually happens in the background. MSDN tells you to tick the Secure by legal entity or by address book. http://technet.microsoft.com/en-us/library/gg731852.aspx This triggers a change in the AOT by enabling two policies.   The reason I mention this is – if you happen to do this in the usr layer. Remember to move it to a layer that will be part of the release.

This is the highlight the affect of  [SysEntryPointAttribute( true )] Switching this parameter to true means that you have to define the permission for all the tables that are used. Otherwise you will get a permission error. Leaving it to false (default), will treat the method as an entry point and give access all access to the used tables. Reference: http://msdn.microsoft.com/en-us/library/sysentrypointattribute.new.aspx