Hi Ernie,
Limited User licenses provide users full read, but limited write, capabilities to all of the licensed solution functionality through any and all modes of access including the Microsoft Dynamics NAV Windows client. The Limited User license is designed to give customers a lower-cost alternative for extending ERP to users who only require limited access to the Microsoft Dynamics NAV application:
• Read access to data contained in the solution through any client accessing the application, including but not limited to the Microsoft Dynamics NAV Windows client, the Microsoft Dynamics NAV Web client, the Microsoft Dynamics NAV SharePoint client, and web services.
• Write access to a maximum of three application tables in the object range 0 – 99,999,999 other than the General Ledger Entry table, through any client accessing the application. Access to the General Ledger Entry Table requires a Full User license.
In fact, write access is denied for the following tables:
• General Ledger Entry (table 17),
• Permission Set (table 2000000004),
• Permission (table 2000000005), and
• Access Control (table 2000000053)
In addition to the 3 mentioned tables above, a Limited User has full write access to the tables mentioned in Appendix A of the document Microsoft Dynamics NAV 2013 and Microsoft Dynamics GP 2013 Licensing Guide..
Dynamics NAV 2013 R2:
===============
Starting with Dynamics NAV 2013 R2, we enforce the limits of a Limited User from the platform. This enforcement is done at runtime, so the write access to the 3 tables depends on the order of write access.
If a Limited User changes a Customer, then adds multiple records to Ship-to Address and creates a Sales Order afterwards, writing to Sales Lines is automatically blocked by the System (this is an example, in fact this process already writes to 3 tables before writing to table Sales Header).
If the Limited User starts a new session and writes to the above mentioned tables in a different order, for example directly creating a Sales Order, he is allowed to create Sales Lines, because this is the second table to write to after Sales Header. If in the process the Limited User writes to one of the free tables mentioned in Appendix A of the above document, this does not count against the limit of 3 tables.
The concurrent user system also applies to Limited Users. So if the same Limited User is connected to the server from 3 Clients, this still counts as only one concurrent user. And also, the enforcement is done in the sessions independently. So you can write to tables A, B, and C in session 1 while writing to tables D, E, and F in session 2. However, I would not count in this behavior in the future, this might change.
Starting with the general availability of Dynamics NAV 2013 R2, partners have to implement version 2013 R2.
Starting with Update Rollup 2 for NAV 2013 R2 You can see which 3 optional tables a limited user has written to when the user receives a permission error because they have exceeded the limit of 3 tables that they can write to. The 3 optional tables that a limited user has written to will be logged in the Windows Event Log.
Note: If you change the license form a NAV 2013 one to a NAV 2013 R2 is mandatory to be uploaded also on the NST server. The steps for changing license will be like: Changed License, Restart, Uploaded License, Restarted NST.
I recommend you to install our latest build CU_14 (388010) so you will be able to identify in the windows applications logs on what tables you have writing to. Also if you want to identify on what tables you are writing when you are working on a workflow I suggest you to use the debugger.
I look forward to hearing from you.
Best Regards, Horia
