jimbow3012,

We recently had a problem with a form showing controls incorrectly for a
user.  Found that rebuilding the index corrected the issue.


Barry.


-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Hardi
Sent: Wednesday, 5 April 2006 9:54 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Re: Urgent Axapta Security Issue

Hi Jim,
I use SP4 and follow your steps (manually from scratch) I found no 
problem the test user can not see "Create BOM" in any way as 
expected.

I am afraid the problem you have is because you created the security 
in non-domain environment and then exported to *.asg file and you do 
import to domain-reated is it? The *asg file generated from non-
domain environment does not have enough information to be used in 
domain related I would think...

In addition I also add restriction "read only" to BOM tables 
directly.

Best regards

Hardi
--- In Axapta-Knowledge-Village@yahoogroups.com, "jimbow3012" 
<[EMAIL PROTECTED]> wrote:
>
> It looks like this may be domain related. Does anyone know where I 
> can directly manipulate the security tokens?
> 
> At issue:
> 
> On the BOM Lines form there is a "Create BOM" button.
> With no domains (no license code) in the security tree you can 
> disable the button and remove it from view by traversing to the 
form 
> in Inventory Management-> Daily -> Bills Of Material -> Lines and 
> set the "Create BOM" to no access and voila its gone from the form.
> 
> Now get the new license key from MS that includes domains.
> Import the license file, wipe out sysinfo data, log in 2tier mode 
> import the license again, set up domain for just the active 
company 
> accounts (Admin domain is set up automatically for all company 
> accounts). Import Security group from non-domain Axapta. Put user 
in 
> the group. Log in as that user and voila - user not only can see 
> the "Create BOM" button, And they can create a new BOM.
> 
> Does anyone have any ideas on how I can fix this issue?
> Microsoft was not helpful, their answer was exactly what I had 
done 
> (create new group, set permissions, follow the security tree as in 
> the no domains, set "Create BOM" to no access, put a user in the 
new 
> group and the "Create BOM" button is still there and functional.
>






Sharing the knowledge on Axapta.
Visit www.frappr.com/axapta for axapta friends. 
Yahoo! Groups Links



 




Sharing the knowledge on Axapta.
Visit www.frappr.com/axapta for axapta friends. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Axapta-Knowledge-Village/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to