I am bit confused. I am trying to delete a company account and i get an
error message that I don't have enough rights to delete table
'ProjInvoiceJour'. (I am part of admin group).
I then checked the security key setup for this table, it is at 'Edit' level.
I can't set it to full control as the button is disabled for admin.
Also, interestingly what I noticed was in Admin security menu under 'Tables'
node, there are many tables which have access set to 'No access'. This is
same in a vanilla version as well.
Does anybody have any idea as how to workaround this? I need to use the
delete company function but I am not going anywhere :(
Thanks
DAXFan
Are you a member of SQL database DBO?
"DAXFan" <DAX...@discussions.microsoft.com> wrote in message
news:8188506B-936B-4279...@microsoft.com...
I encountered the same problem a while ago. Do you only have one group
'Admin' in the security or do you have multiple groups? In my case I could
only delete a company when I had only one usergroup attached to my
user-account in AX.
It seems there is a problem with security rights in AX2009 SP1 when you have
more than one user group attached to a user. We had also problems when we had
upgraded to SP1. Some users could not post project journals anymore. The day
before upgrading there was no problem. Ans we did not chage anything in the
user group permissions.
regards,
André
You may enable it: Open AOT\Forms\SysUserGroupSecurity\Methods
There you'll find a method called "isAdmin".
Change the code so that this method will always return false and you should
be able to edit the security keys for the admin usergroup.
this is a knows problem (in the community).
Please try the following:
http://www.doens.be/2009/04/security-key-disabled-for-admin/
It's the same as Philipp said.
In addition you can, if you know what you are doing!!!!, disable the
configuration key which controls the security key. After you have disable the
configuration key and enabled the configuration key once again, should should
have access to it.
But be careful!!! When you are going this way, there is a big chance to lose
all the data stored in table which gets "disabled" by the configuration key
(when you disable the configuration key).
--
Sincerely yours
Axel Kühn (visit my Dynamics AX blog at: http://blog.ak-home.net)
And did you already find a solution ?
Andr? Arnaud de Calavon wrote:
Hi DaxFan,I encountered the same problem a while ago. Do you only have one
09-Oct-09
Hi DaxFan,
I encountered the same problem a while ago. Do you only have one group
'Admin' in the security or do you have multiple groups? In my case I could
only delete a company when I had only one usergroup attached to my
user-account in AX.
It seems there is a problem with security rights in AX2009 SP1 when you have
more than one user group attached to a user. We had also problems when we had
upgraded to SP1. Some users could not post project journals anymore. The day
before upgrading there was no problem. Ans we did not chage anything in the
user group permissions.
regards,
Andr??
"DAXFan" wrote:
Previous Posts In This Thread:
On Thursday, October 08, 2009 5:56 AM
DAXFan wrote:
Security keys disabled for Admin account!
Hi All,
I am bit confused. I am trying to delete a company account and i get an
error message that I do not have enough rights to delete table
'ProjInvoiceJour'. (I am part of admin group).
I then checked the security key setup for this table, it is at 'Edit' level.
I cannot set it to full control as the button is disabled for admin.
Also, interestingly what I noticed was in Admin security menu under 'Tables'
node, there are many tables which have access set to 'No access'. This is
same in a vanilla version as well.
Does anybody have any idea as how to workaround this? I need to use the
delete company function but I am not going anywhere :(
Thanks
DAXFan
On Thursday, October 08, 2009 5:59 AM
DAXFan wrote:
BTW, it is a AX 2009 SP1 installation."DAXFan" wrote:
BTW, it is a AX 2009 SP1 installation.
"DAXFan" wrote:
On Thursday, October 08, 2009 6:36 AM
Newbie wrote:
HiAre you a member of SQL database DBO?"DAXFan"
Hi
Are you a member of SQL database DBO?
On Thursday, October 08, 2009 7:08 AM
DAXFan wrote:
I am not. But AX AOS machine account is.I do not think individual users need
I am not. But AX AOS machine account is.
I do not think individual users need to have the DBO rights at SQL level. The
security checks are done at the AX level.
"Newbie" wrote:
On Friday, October 09, 2009 2:01 AM
Andr? Arnaud de Calavon wrote:
Hi DaxFan,I encountered the same problem a while ago. Do you only have one
Hi DaxFan,
I encountered the same problem a while ago. Do you only have one group
'Admin' in the security or do you have multiple groups? In my case I could
only delete a company when I had only one usergroup attached to my
user-account in AX.
It seems there is a problem with security rights in AX2009 SP1 when you have
more than one user group attached to a user. We had also problems when we had
upgraded to SP1. Some users could not post project journals anymore. The day
before upgrading there was no problem. Ans we did not chage anything in the
user group permissions.
regards,
Andr??
"DAXFan" wrote:
On Friday, October 09, 2009 4:44 AM
Philipp wrote:
You may enable it: Open AOT\Forms\SysUserGroupSecurity\MethodsThere you will
You may enable it: Open AOT\Forms\SysUserGroupSecurity\Methods
There you will find a method called "isAdmin".
Change the code so that this method will always return false and you should
be able to edit the security keys for the admin usergroup.
On Thursday, October 15, 2009 11:44 AM
Axel K?hn wrote:
Hi,this is a knows problem (in the community).
Hi,
this is a knows problem (in the community).
Please try the following:
http://www.doens.be/2009/04/security-key-disabled-for-admin/
it is the same as Philipp said.
In addition you can, if you know what you are doing!!!!, disable the
configuration key which controls the security key. After you have disable the
configuration key and enabled the configuration key once again, should should
have access to it.
But be careful!!! When you are going this way, there is a big chance to lose
all the data stored in table which gets "disabled" by the configuration key
(when you disable the configuration key).
--
Sincerely yours
Axel K??hn (visit my Dynamics AX blog at: http://blog.ak-home.net)
"DAXFan" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Cholesterol - HDL versus LDL in Women
http://www.eggheadcafe.com/tutorials/aspnet/c57da08f-1bab-4e13-8c17-8460b9a2d04c/cholesterol--hdl-versus.aspx