How Restrict read Data on SQL Server level?

KeeperRU
KeeperRU Member Posts: 58
edited 2014-05-23 in NAV/Navision Classic Client
Hello, here is the task.

Suppose, I don't want that users can browse information about few Vendors (in ledger tables, documens etc).
Those Vendors have attribute - "Hide Entries"

There are solutuions:
1) Create FlowField "Hide Entries" - in every table where I need restrict reading Access, and filter this Field on OpenForm
= Filter on FlowField it's very slow....

2) Create Normal Field - in every table where I need restrict reading Access, and filter this Field on OpenForm
= very hard and expensive, because I need to find every INSERT,MODIFY in code for this tables, and fill this field.

3) ????
Maybe there is way to modify READ from SQL Server on this tables and edit this Query?

4) ???
Something else?

Comments

  • kine
    kine Member Posts: 12,562
    This is more complicated than you think. What about posting - if the last entry is filtered out, how the posting will go? (when it is taking last entry to set correct entry no. on new entry) etc...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • KeeperRU
    KeeperRU Member Posts: 58
    kine wrote:
    This is more complicated than you think. What about posting - if the last entry is filtered out, how the posting will go? (when it is taking last entry to set correct entry no. on new entry) etc...

    OK, I get it.
    But how work Security Filter on Permissions Form?
    Security Filter doesn't affect posting or nobody shall secure Ledger tables (because of what you said).
  • kine
    kine Member Posts: 12,562
    It is why I never used security filters and I recommend to not use them, because the setup is so complex and in most cases doesn't lead to requested result.

    In NAV 2013 were security filters extended and are more usable, because you can set if the record variable could ignore them etc...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • KeeperRU
    KeeperRU Member Posts: 58
    Thanks,
    I would combine my 1) and 2) solution.
    I test it, and filtering on FlowFields not so bad - if Table store not so much entries.
  • william_akihisa
    william_akihisa Member Posts: 14
    Like Kine said,
    using security filter is bad idea,it's hard know each link data when every proses running in nav, even with standard posting documents like sales or purchase. if you using navision classic, i suggest limit access with navigation pane designer, or if you using new RTC client you can limit access by page action or view with user setup much more safe.

Categories