Counting Named Subscription Users in NAV – 2nd part

In my previous post, I tried to explain how to handle with named users in NAV. But I’ve got a few feedbacks with some additional questions I didn’t cover in this text.

The main question was what if I want to stop to use some account temporary, for example because sick leave or vacation or something similar? In this case, we can disable this user.

DisableNamedUsers

When you try to login the next time, you can see system will not count disabled users. Then you can decries number of users for some period. When your user come back, you need to increase number of users in your license and just enable this user.

Second very important topic is that you must to know when you buy for example 3 subscription users, you will get 5 (you will get 2 users for free, but with limited usage). This is because 1 user is for intended for partner work and 2nd users is for external accountant, but remember an EXTERNAL accountant. You need to create them on beginning to avoid misuse of license rights and use it for internal processes.

And on the end, if you already have the maximum number of full users and want to create new limited user, because you have licensed more limited users, anyway you will get message that this is not possible because the new user don’t meet the terms of the current license.

##1

This is only because of that, Full User is default user. You just need to change License Type option to Limited and it will be OK.

Advertisements

Counting Named Subscription Users in Dynamics NAV

Waiting Dynamics NAV as full SaaS solution (Dynamics 365 ‘Tenerife’), a lot of partners are deploying NAV on Azure with subscription licenses. Subscription license has much better price in comparison with perpetual model, even from only BREP.

But we have a small difference here. In perpetual licensing model, users are concurrent, but n subscription model, users are named. Because of that I’ve got a lot questions how system count these users and prevent bigger number of users from licensed.

Generally, this is very easy. NAV counts number of created users and compare it with your subscription license. That moment, when you try to create new user, more than you have licensed, system will stop you.

##1

As you can see on the previous picture, I’ve got a message that creating this new user will not meet the terms of the current license. OK, it works. That means if you want to change user, you need to delete old one and than create new one.

But in subscription model, you can change number of users monthly. What if you had in one moment, because of business needs, more licensed users and now you scaled down number of users? In this case, when you try to log in, system will show the following message:

##2.PNG

That means with current license and number of users, you are not legal. But if you press OK, system will allow you to log in. But every time when you try run NAV, you will get this violation message that shows you are not legal.

How to Configure Limited Users in NAV?

A few days ago I’ve wrote about new possibilities in using of Limited Users in NAV 2016. I think this is big improvement, because we can use limited users for much more roles.

But I got a few comments about configuration limited users. OK, you can configure users as limited and this is all. Nothing more.

l-1.jpg

But people wants to configure what three additional application tables these limited users can use. Base on the standard NAV, this is not possible. These users get write access to a maximum of three application tables in the object range 0 – 99,999,999 other than the General Ledger Entry table. But system will count the first three used application tables beside the default tables. This is counted by the session. That means, users can use different three application tables in different sessions.

Some of administrators still want to limit these users on some specific tables. There is not feature for this requirement, but it can be made using User Permission Sets. We can create one permission set with all read permission on all tables (or less if you want this). Then, we can configure additional permission set with all permissions (insert, modify, delete) on our default 151 application tables. And on the end we can configure specific permission set based on our requirements for three additional tables.

Every time when we want to configure new limited user, we just need to add him these first two permission sets and one specific for him (or his role). In this case this limited user will have read permission to all tables and all other permissions to default tables and three we added to him. In this case, his three application tables will not depends of his first usage in session.

This is not some specific feature, but it is useful work around solution for configuration.

Limited Users in NAV 2016

I suppose the most of you have already used Limited Users. It is pretty good possibility to save some money for users who have not a lot different processes to work in NAV. But limitation was a big; you could insert in only 3 tables by your need and in 80 additional by default. It was enough for some basics processes (creating contacts, HR, warehouse and similar).

But from NAV 2016, we have a pretty greater possibilities. That means we can use for inserting even 151 default tables; you can find completely list here. Some of the most important default tables for insert are:

  • Customers and Vendors
  • Customer and Vendor Invoice Discounts
  • Sales and Purchase Headers and Lines
  • Deferrals
  • Sales/Puchase Price and Line Discount
  • Assembly Order Headers and Lines
  • Incoming Documents
  • Workflow tables

You can see that with these tables in combination with three additional by your needs, we can use Limited Users for a lot different processes. It can decrease project cost and improve quality.

LimitedUsers.jpg