User gets this error when opening NAV every time. After clicking 'OK' everything is fine.
This isn't a role permission issue as the users roles are golden.
I found some suggestions online saying to delete the records in the table mentioned. They're saying the license we have may not cover that data.
Some solutions recommend deleting data from the aforementioned table.
delete FROM [NAV].[dbo].[CompanyName$Account Schedules Chart Setup]
But I'd like to understand the problem better before I go deleting rows.
I was hoping for an application side fix as well. But I'm not familiar with the 'Finance Performance' window of NAV or 'Account Schedules Chart Setup'.
0
Answers
and thought I'd try giving the user SUPER permissions.
After that the problem was solved?! hooray.
naturally this user cannot keep the SUPER permission.
Any idea how to narrow down the 'exact permission' needed for the role?
Could I run a trace or something to see that?
https://m.youtube.com/watch?v=FJSE500nX5w
https://olofsimren.com/record-permissions-in-nav-2016/
https://totovic.com/2015/10/13/automatic-recording-permissions-in-nav-2016/
https://saurav-nav.blogspot.co.uk/2015/05/nav-2013-r2-role-permission-wizard.html#more
I also found a temporary work around by creating a new permission set and assigning it only Table data 'READ' for tableID 762.
I'll check that link out for a more permanent fix and/or better understanding.
I think the root problem of this error is a combination of two factors.
1) You have at least one record if table "Account Schedules Chart Setup"
2) Your license don't have permission to read that table
To confirm this, try to open that table with customer license. If a permission related error occurs, check if there is at least one record (query directly at sql server client).
The solution is delete this record.
This occurs when you use a "developer license" or a license that have the "Account Schedules" granule. Some function in nav will create a setup record if don't exists one. After change do "customer license" you will get this errors because no setup record should exists.
Regards and good luck.
parm