User Permissions

gwmadre
gwmadre Member Posts: 13
When I add a table permission to an existing role in NAV it changes the value in Run Permission to yes. This is a non editable field and won't allow you to change the value to blank or indirect. However, the value for this field in all of the existing table permissions is blank. Can someone explain this behavior?

I'm using 5.01 with SQL server.

Comments

  • kriki
    kriki Member, Moderator Posts: 9,135
    Are you sure it is "Table" and not "TableData"?
    In "TableData" it is normal that Execute is disabled. You can't "execute" data, only the code in the "Table".
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • gwmadre
    gwmadre Member Posts: 13
    Yes. It is Table Data. Why does NAV make Run Permission "yes" on all new lines you add to the permission table?
  • jannestig
    jannestig Member Posts: 1,000
    Did you look at the table and the fields in table 2000000005 permissions?

    The initval is set to "yes" it was probably a decision made by a development manager in MS, if its really that big a hassle you can probably change the value to NO or blank
  • David_Singleton
    David_Singleton Member Posts: 5,479
    gwmadre wrote:
    Yes. It is Table Data. Why does NAV make Run Permission "yes" on all new lines you add to the permission table?

    It depends on HOW you add them. Manually they are set to NO, but if you select the All Objects Button then its sets to no.

    It has no effect, so just learn to ignore it.
    David Singleton
  • gwmadre
    gwmadre Member Posts: 13
    Yes. Over the years I have learned to ignore it but users continue to ask the question so I thought it would be good to know why.