Nav SP1 role permission

jan_kjan_k Member Posts: 3
edited 2008-06-13 in SQL General
I try to implement role for user that he/she could process sales orders by giving them all roles that concern sales order processing. Althought roles include all permission for table 246 Requisition line, I receive message "You do not have permission to read table Requisition line".

After giving roles and permission, I have run "synchronize all login" and even test if I grant select on Sql Server table, but no effect. Also I created role for codeunit 5790, but that is maybe not the way to handle it.

Could it be some granule issue? This table 246 have some line data.

Enviroment is: Nav SP1/Sql Server 2000

Error occur in codeunit 5790, function:
CalcScheduledReceipt(VAR Item : Record Item) : Decimal

Sql statement:
SELECT SUM("Quantity (Base)") FROM "Company Name$Requisition Line"
WHERE (("Type"=?)) AND (("No_"=?)) AND (("Variant Code"=?)) AND (("Location Code"=?))
AND (("Planning Line Origin"=?)) AND (("Due Date">=? AND "Due Date"<=?))

Comments

  • krikikriki Member, Moderator Posts: 9,112
    [Topic moved from Navision forum to SQL General forum]

    BTW : if you use 5.0SP1, you better use SQL2005! SQL2000 has some problems with indexed views.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • WaldoWaldo Member Posts: 3,412

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • jan_kjan_k Member Posts: 3
    Enviroment is Nav 4.0 SP1
  • WaldoWaldo Member Posts: 3,412
    4.0SP1 means that you're working with "advanced" security ... which is actually not really easy to work with.

    The best thing to do (imho) is to do a runtime upgrade to the latest version. Can be 4.0Sp3Update6.9 or 5.0Update1.5 (for more info, I would like to refer to my blog, where you can find a table with platform updates).

    Please, do not use 5.0Sp1,because it's not recommended on SQL2000 as mentioned above.

    If you do this, you can use the "standard" security model instead of the current "enhanced" security model. This will get rid of your security pains.

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
Sign In or Register to comment.