Limited Users in 2013 R2

Miklos_Hollender

Has someone tested this for major processes like enter sales orders, post sales orders, etc. ? It is not possible to test it without buying it and of course buying it without knowing exactly if it will fit is obviously not an option.

For example what about indirect modification like postinging shipments, invoices creating many Entry tables?

We can guess from the list of "free" tables what they "meant" it for. It looks like order entry yes, order posting probably not.

Appendix A includes:

51 User Time Register
97 Comment Line
309 No. Series Line
337 Reservation Entry
355 Dimension Ledger Entry
356 Journal Line Dimension
357 Document Dimension
358 Production Document Dimension
359 Posted Document Dimension
361 G/L Budget Dimension
389 Service Contract Dimension
405 Change Log Entry
480 Dimension Set Entry
481 Dimension Set Tree Node
952 Time Sheet Detail
953 Time Sheet Comment Line
5050 Contact
5051 Contact Alt. Address
5052 Contact Alt. Addr. Date Range
5054 Contact Business Relation
5061 Rlshp. Mgt. Comment Line
5062 Attachment
5065 Interaction Log Entry
5072 Campaign Entry
5075 Logged Segment
5078 Segment History
5080 To-do
5106 Document Dimension Archive
5107 Sales Header Archive
5108 Sales Line Archive
5109 Purchase Header Archive
5110 Purchase Line Archive
5123 Inter. Log Entry Comment Line
5125 Purch. Comment Line Archive
5126 Sales Comment Line
5151 Integration Record
5199 Attendee
5648 FA Allocation Dimension
5766 Warehouse Activity Header
5772 Registered Whse. Activity Hdr.
5773 Registered Whse. Activity Line
6550 Whse. Item Tracking Line
7135 Item Budget Dimension
7312 Warehouse Entry
7313 Warehouse Register
7318 Posted Whse. Receipt Header
7319 Posted Whse. Receipt Line
7320 Warehouse Shipment Header
7321 Warehouse Shipment Line
7322 Posted Whse. Shipment Header
7323 Posted Whse. Shipment Line
7324 Whse. Put-away Request
7325 Whse. Pick Request
7354 Bin
2000000067 User Default Style Sheet
2000000068 Record Link
2000000073 User Personalization
2000000075 User Metadata
2000000080 Page Data Personalization


This looks like to me that

1) indirect access is also counted. because nobody makes a posted warehouse shipment directly.

2) Order entry should be OK, posting probably not, due to the many Entry tables

3) I don't quite understand the warehouse stuff. OK you can create a posted whse shipment. It suggests posting at least with ship, not invoice. For that you need besides these item ledger entry, value entry, item register, bin content, and whatever else. I think that would not work?

Rob_Hansen

In my opinion, Limited Users had a limited amount of thought and planning put into them. The arbitrary 3 table rule and some of the strange exempted tables have me thinking that the group that designed them didn't really know what they wanted them used for. We're treating them as read only users, or users with VERY light data entry needs (update customers, other master tables, etc.). As soon as the topic of the user entering orders or any more advanced functions comes up, we're quoting full users.

I would love the NAV team blog to post a topic showing some of the processes that limited users CAN be used for along with any tradeoffs/exceptions (i.e. order entry so long as certain factors don't come into play).

Miklos_Hollender

@rdhansen I think a basic sales order entry should work with this. I think this is why reservation entry, sales order archive, sales comment were indcluded. Releasing (warehouse request) makes it 3. When approvals is used that is too much but I think for basic order entry it should work?

I mean the fact sheet specifically says remote sales people

kine

Had no time to test it, but you should be able to create the documents. Of course, you cannot post them, because it will create G/L Entries (which are forbidden for limited users), but in case of warehouse documents (without automatic adjustment), may be it could work. But again, the limited user is really "one purpose" user, doing just one thing in the system (creating one type of documents, modifying just customer card, just registering time, etc.)

pdj

Why not simply create a role (sorry, permission set) with these tables and test it?

tinoruijs

I think you can test with the demo-license.
NAV starts to count the modified tables from each new login in NAV.
So you can change 10 tables if you want, but you'll have to login 4 times.

kine

pdj wrote:

Why not simply create a role (sorry, permission set) with these tables and test it?

It is simplier: just set the correct licence type on the user...

tinoruijs

I'm curious if anybody has got a working limited user posting a warehouse receipt for example?
I thought posting a warehouse receipt should be possible, but I'm in doubt because there can be journals created when receiving a purchase order. But when Expected cost to GL is off, I thought it should work.