Hello,

Thanks a lot for your reply.

I have done it using hasSecurityKeyAccess (securitykeyId, Accesstype) function. 

Regards,
Sam



________________________________
From: Ruel Ormita <r...@msb.com.my>
To: development-axapta@yahoogroups.com
Sent: Mon, 15 March, 2010 4:46:41 AM
Subject: RE: [development-axapta] Security Key

  
Hello,

Don’t need the profiler. Just check the user account inside ax then check what 
is his permission.

Ruel

From: development- axa...@yahoogrou ps.com [mailto:development- 
axa...@yahoogrou ps.com] On Behalf Of Hemant Kumthekar
Sent: Friday, March 12, 2010 10:31 PM
To: development- axa...@yahoogrou ps.com
Subject: Re: [development- axapta] Security Key

Hi,

There is a security profiler tool which can be used to check the access. You 
need to get that from Microsoft support. 

Hemant

____________ _________ _________ __
From: shamika <shamik...@yahoo. com <mailto:shamikask% 40yahoo.com> >
To: development- axa...@yahoogrou ps.com <mailto:development -axapta%40yahoog 
roups.com> 
Sent: Thu, March 11, 2010 2:29:07 PM
Subject: [development- axapta] Security Key

Hello,

I wanted to check security key access of logged-in user.
Lets say, userId is dev11. Then I want to check whether dev11 has full access 
for security key, say "VendKey" (which is maintained in some table as a 
parameter). 
Does anybody have an idea about how to do the same?
Please let me know.

Thanks in advance,

Sam

[Non-text portions of this message have been removed]

__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 4944 (20100314) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset. com

__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 4944 (20100314) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset. com

[Non-text portions of this message have been removed]


 


      The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. 
http://in.yahoo.com/

[Non-text portions of this message have been removed]

Reply via email to