Session Table Permissions

Business Central/NAV Developers Forum
1

Hi, I am using the Session virtual table to lookup the user’s connection id to give me a unique value for populating a table. Everything works fine when logged in as Administrator but when logged in as a normal user I get ‘You do not have permissions to the Session table’, even though the user has the Navision ‘SUPER’ role. I have got around the problem by making the SQL users DBOs, but obviously this is not an acceptable solution. Can anybody tell me what SQL permissions are required for the Session table. Using : Navision 4.00, SQL 2000 Any help appreciated, Jonathan

2

Try adding READ permission to the Session Table through the Permission property of the object which is reading the Session Table to populate you other table …

3

Thanks for the reply, however when I try to add permissions to the CodeUnit for the Session table it says ‘You do not have permission to read the Session table’ when trying to compile/save. Any other ideas?

4

Because if you want to add some permissions, you must have it in licence. Try to add only read permissions, not insert, modify, delete…

5

Hi, did you login as administrator when you assign session table permission to the codeunit??

6

I have encountered the Session Table permission problem on a native database.

The solutions given above are for databases on SQL Server. On native server, a SUPER user does not see the error message, but other users do.

I added Read and Delete permissions on the Session table explicitly in the ALL role, without seeing any change.

I then tried adding permissions in the codeunit, but when I try to save the codeunit I see the error message (even if I have SUPER role): "You do even the SUPER user gets “You do not have permission to read the Session table.”

Do you know how of any solution that works on native databases?

7

I was able to resolve the same problem in native database by adding read permission to Tabledata | 2000000009 | Session.

8

Hi everybody,

I encountered the same problem and solved it by creating an additional role only containing read permission to Tabledata | 2000000009 | Session. An important thing I noticed is, that this only seems to work when an explicit role for read permission on Table “Session” is created and this role is not limited to a single company, ie you have to leave the “company” field empty.