When you import a new security key trough a XPO, this new key will be disabled even for the admin group. Since you can’t adjust the security setting for the admin group you can’t use the keys functionality.
There is a verry simple solution for this problem. Open the method \Forms\SysUserGroupSecurity\Methods\isAdmin and force this method to return false.
#admin
boolean isAdmin()
{
/* if (userGroupInfo.Id == #AdminUserGroup &&
(domainInfo.Id == #AdminDomain || !useDomains))
{
return true;
}*/
return false;
}
Subscribe to:
Post Comments (Atom)
How to identify the user that was used to change an object from AOT in AX2012
Get the object name for which we need to track these (user and date&time) information's. Login to SQL Server Management Studio an...
-
The global search is a feature in Dynamics Ax 4.0 which allows you to search for a string in several tables (like a full text search). You s...
-
A while ago I had the need to translate labels, I was creating eMail bodys while using SysMailer and wanted to use different languages for d...
-
This article explains: How to picking list through a job using X++ in Dynamics AX. Applied on: Dynamics AX 2009 SP1 Create a job a...
No comments:
Post a Comment