Permission differences between 5.0SP1 and former versions

Slawek_Guzek
Member Posts: 1,690
Hi all,
I've found recently that there is significant difference in permission behaviour between newest NAV 5.0SP1 and any former version. It is really nasty surprise
Calculation of Flowfields values requires now direct R permission to the FlowField source table, or Indirect permission on the table with direct read on the form.
This is the problem in all the situations when users are allowed to see summed values, but are not allowed to drill down to the details.
Let's see Customer Card as an example. In v4.0x and 5.0 it is enough to have indirect read for table 379 (Detailed Cust. Ledger Entry) to see Balance (LCY) field on Customer Card.
In version 5.0SP1 I was forced to either set direct read on T379, or add T379=R in the Permission property on Form21 (Customer Card) to be able to open Form21
Any clue how to workaround this ?? I don't want to modify all necessary forms (in practice i need to modify all forms where any FlowField is displayed), and I'm not allowed to give direct R because this will give users access to the details.
Regards,
Slawek
I've found recently that there is significant difference in permission behaviour between newest NAV 5.0SP1 and any former version. It is really nasty surprise

Calculation of Flowfields values requires now direct R permission to the FlowField source table, or Indirect permission on the table with direct read on the form.
This is the problem in all the situations when users are allowed to see summed values, but are not allowed to drill down to the details.
Let's see Customer Card as an example. In v4.0x and 5.0 it is enough to have indirect read for table 379 (Detailed Cust. Ledger Entry) to see Balance (LCY) field on Customer Card.
In version 5.0SP1 I was forced to either set direct read on T379, or add T379=R in the Permission property on Form21 (Customer Card) to be able to open Form21
Any clue how to workaround this ?? I don't want to modify all necessary forms (in practice i need to modify all forms where any FlowField is displayed), and I'm not allowed to give direct R because this will give users access to the details.
Regards,
Slawek
Slawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
0
Comments
-
Are you using Standard or Extended security model?0
-
Tried both, got the same resultsSlawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030
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