Removing fasttabs on pages for chosen roles
gravecz
Member Posts: 35
Hi,
i was trying to remove fasttab Invoicing on Item card (page 30) for role "ABC".
I started configuration mode and thought that if i customize page in configuration mode of role "ABC", then fast tab invoicing will be removed just in this role, but it's not true. It removes fasttab Invocing for each role, what is unexpected behavior for me.
Is there any way how to remove fasttab just for chosen roles?
Martin
i was trying to remove fasttab Invoicing on Item card (page 30) for role "ABC".
I started configuration mode and thought that if i customize page in configuration mode of role "ABC", then fast tab invoicing will be removed just in this role, but it's not true. It removes fasttab Invocing for each role, what is unexpected behavior for me.
Is there any way how to remove fasttab just for chosen roles?
Martin
0
Comments
-
you can create boolean variable
and then put it in the openpageAccessControlRec.RESET; AccessControlRec.SETRANGE(AccessControlRec."Role ID",'ABC'); AccessControlRec.SETRANGE(AccessControlRec."User Name", USERID); IF AccessControlRec.FINDSET THEN yourvariable := TRUE ELSE yourvariable := FALSE;
and then put yourvariable in the properties of your fastabs0 -
casanova - Yes, of course that can be done...but it defeats the whole purpose of configuration. In classic NAV, changes like this had to be done using customization like what you're suggesting. One of the big selling points of the RTC is the ability to configure these sorts of changes for roles without development time/customization. Developers are often quick to suggest these sorts of customized approaches...but unnecessary customization is bad for everyone.
Sorry...my comment was related to that second post. I don't have anything to offer on the original one - i would have expected the changes to just apply to the ABC role. You had assigned your user to that profile before configuring it...correct?Rob Hansen
http://www.epimatic.com0 -
rdhansen wrote:casanova - Yes, of course that can be done...but it defeats the whole purpose of configuration. In classic NAV, changes like this had to be done using customization like what you're suggesting. One of the big selling points of the RTC is the ability to configure these sorts of changes for roles without development time/customization. Developers are often quick to suggest these sorts of customized approaches...but unnecessary customization is bad for everyone.
Sorry...my comment was related to that second post. I don't have anything to offer on the original one - i would have expected the changes to just apply to the ABC role. You had assigned your user to that profile before configuring it...correct?
no choice must do this way i guess
for permission set only allow until table level
but in your case for field level0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 322 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions