Hello everyone,
I have a hard time setting up the security on JetReports.
Basically, I thought after reading the forum that JetReport was using the same permission as NAV, i.e. if someone has not the permission to see G/L entries in NAV, he would not be able to generate a financial report in JetReport. But this is not the case, since everyone can generate every reports.
The only thing that can't be done is using the drilldown (Dynamic NAV classic client) on a G/L entries that has been generated. WHen I use the drilldown, I get an error message on NAV stating I don't have permission for these data. The drilldown is working with the Jet data grid.
In the end, is it possible to restrict the ability of users to generate reports?
Thank you,
Mathieu
Date
Votes
3 comments
-
Jet Reports Historic Posts Hi Mathieu,
Jet Essentials does respect NAV table permissions. I'm guessing in your case, NAV is set up so that certain users cannot access G/L entries in the NAV user interface. However, the underlying tables such as G/L Entry must not have permissions set on them because Jet does respect the permissions on the tables. Since Jet does not have any way to run the NAV code being used in Forms or Pages, to restrict users, you must have permissions set up on the tables themselves for Jet to see those permissions. Does this make sense?
Regards,
Hughes -
Jet Reports Historic Posts Hello Hughes,
After checking the permissions for the user I tested on, there are no permission set on tables G/L Entry or any other tables linked to Finance.
Do you have any idea of where the problem could come from?
Thank you,
Mathieu -
Jet Reports Historic Posts Hello Matthieu,
I don't understand what you're asking. You said you have a user who can't access the General Ledger in NAV, but he can access it in Jet. I said that this is probably because he is locked out in NAV through code that is running in the NAV user interface (on the form or the page) rather than actual restrictions on the tables. Jet has no way to detect restrictions being implemented at the user interface level in NAV. Jet can only respect permissions being applied to the tables themselves.
Now you say that you have checked and the user in question has no restrictions on the actual table, which makes perfect sense. The fact that the user has no restrictions on the table is the reason that they are able to report off the table in Jet. If you want the user to be unable to access the table in Jet, then you need to add permissions to the table to restrict that user. Does this make sense? Is there something else I am missing?
Regards,
Hughes
Please sign in to leave a comment.