Microsoft Dynamics Nav (Navision)
Jet Reports and NAV Security
Options for setting up NAV security to for Jet Reports for NAV 2009 R2 and earlier
Microsoft NAV 2009 R2.
How to setup NAV permissions to enable Jet Report Data Source connectivity for databases with multiple companies for NAV 2009 R2 and earlier.
With NAV 2009 R2 and earlier versions, Jet Reports requires that users have read access to the company table 2000000006 for all companies. If a user’s Database login or Window login has been setup with security “Roles” where company filters have been applied, when attempting to setup a Jet Report data Source and the “Test Connection” function is triggered, the following error is displayed: “You do not have permissions to read the Company table.”
Specifically, when setting up NAV security, the “All” or “Basic” roles have the required permissions for the company table 2000000006. However, if the “All” or “Basic” role has a company filter, then the Jet Report Data Source cannot be configured properly.
To resolve this permission issue, create a new role called “JetReports-Access” (or whatever name makes sense) and grant “read” permission to the table data 2000000006. This role would then be applied to the specific users who need Jet Reports access and connectivity.
Note there is one anomaly with this solution. Users who are granted the “JetReports Access” role will be able to see all companies when the user accesses the company drill down list under File>Company>Open. However, if the user does not have any roles granted to a specific company, even though the company name can be viewed from the drop down list, the user will not be able to gain access.
NAV 2013, NAV 2013 R2 and NAV 2015
A similar issue has been discovered for NAV 2013, NAV 2013 R2 and NAV 2015 for users who have been setup with a Jet Reports data source connection type for “Direct SQL Server” for jet reports versions 2015 and 2015 update 1. A similar scenario would occur for users who have been setup with permissions that limit access to specific companies. The best resolution is to un-install the user’s current Jet Reports version and install Jet Report’s latest release to correct this issue. Alternatively, a new permission set could be setup to grant permissions for table data 2000000006 with full company access, similar to the sample one above.
Written by Mark Stept