Solved: Opening Item Card Page 30 non-editable depending on user-rights

FragenFrager
Member Posts: 67
Hello,
one of our customers has had the article card changed in version R2 in the Nav so that it can be edited or not depending on a code in the user equipment. This is ultimately possible with a simple CurrForm.EDITABLE ( identifier from the user setup ).
Unfortunately, this does not work in the NAV 2018; You can open the page in non-editable mode, but unfortunately this can be overridden with the edit button.
I have now managed to dynamically control the editable property for the individual groups. Unfortunately, articles can still be created or even deleted if the user is reading only.
This was covered in the old version with the CurrForm.EDITABLE and must definitely work in the new version.
Is there a possibility?
one of our customers has had the article card changed in version R2 in the Nav so that it can be edited or not depending on a code in the user equipment. This is ultimately possible with a simple CurrForm.EDITABLE ( identifier from the user setup ).
Unfortunately, this does not work in the NAV 2018; You can open the page in non-editable mode, but unfortunately this can be overridden with the edit button.
I have now managed to dynamically control the editable property for the individual groups. Unfortunately, articles can still be created or even deleted if the user is reading only.
This was covered in the old version with the CurrForm.EDITABLE and must definitely work in the new version.
Is there a possibility?
0
Answers
-
How this page is run? if you can manage to run from a codeunit or something then you could do a could in the codeunit
Pagevar.EDITABLE := FALSE (depending on the users setup)
Pagevar.RUN;United Kingdom0 -
The page 30 is run directly from the list page 31, I'm not sure if this standard-behaviour can be overridden, but I will give it a try, thanks.0
-
You might need to run the page 31 in the editable = false mode.United Kingdom0
-
Hello Developer101,
due to the specialities of the customer I made the groups editable by parameter and prevent specific users from inserting/deleting an Item by an error-message, which is gerenated in the OnInsertRecord- / OnDeleteRecord-Trigger of Page 30.
Thanks.0 -
OK that is great, that was another of doing it.United Kingdom0
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
- 320 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