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
- 300 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
error no modify permission to custom report layout table
Karenh
Member Posts: 209
In NAV 2016 I have set up about 10 custom report layouts. Occasionally a user will go to print and gets the error message: You do not have the following permissions on TableData Custom Report Layout: Modify.
This occurs with different custom report layouts, not always the same one. From screenshots, I can see that they are in the Sales Order page or similar, not custom report layouts page.
None of these users have modify permission to the custom report layout table as we do not want them making changes to the custom reports.
To resolve it, they exit NAV, log back in and then can usually print.
Does anyone have an idea of what could be causing this?:
This occurs with different custom report layouts, not always the same one. From screenshots, I can see that they are in the Sales Order page or similar, not custom report layouts page.
None of these users have modify permission to the custom report layout table as we do not want them making changes to the custom reports.
To resolve it, they exit NAV, log back in and then can usually print.
Does anyone have an idea of what could be causing this?:
0