Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV2009R2 security filter on Ledger Entries
entropus
Member Posts: 10
http://msdn.microsoft.com/en-us/library/dd355364.aspx
I set up security filter for Vendor Ledger Entries (25) and Detailed Vendor Ledg. Entries (380) according to the procedure above.
Permission to read tables 25 and 380 were added to CU 90.
Indirect permission to read tables 25 and 380 were added to roles.
While posting a purchase invoice I get an error stating I don't have permissions to read Vendor Ledger Entry table.
When I switch to classic client and debug, the debugger stops and CU 90 and code VendLedgEntry.FINDFIRST.
What could be the solution?
I set up security filter for Vendor Ledger Entries (25) and Detailed Vendor Ledg. Entries (380) according to the procedure above.
Permission to read tables 25 and 380 were added to CU 90.
Indirect permission to read tables 25 and 380 were added to roles.
While posting a purchase invoice I get an error stating I don't have permissions to read Vendor Ledger Entry table.
When I switch to classic client and debug, the debugger stops and CU 90 and code VendLedgEntry.FINDFIRST.
What could be the solution?
0
Comments
the problem is that the security filter is page-wise (or so). The result is that more records are marked as forbidden than should be. The only solution was to remove the security filters, and change the posting process for the "restricted" postings to G/L.
with best regards
Jens
the problem is that the security filter is page-wise (or so). The result is that more records are marked as forbidden than should be. The only solution was to remove the security filters, and change the posting process for the "restricted" postings to G/L.
with best regards
Jens
Thanks for updating this. Could you explain this a bit more
""The only solution was to remove the security filters, and change the posting process for the "restricted" postings to G/L.""