Skip to main content

NAV 2013 & Later - Restrict Multiple Login for same User ID.

Hi All,

This is nothing most of you would be interested in. This post only show steps about how to Restrict a User to Login into Navision Database From Same User ID.

If you don't know this, then please go ahead.

The intended readers for this post are the Peoples who have recently joined and are still Learning NAV. Based on Request received via Contact Form..




In NAV 2013 and Later Microsoft we can get this information via a table named as Active Sessions (Table ID - 2000000110).

This table contain information about all the active session into the database.

For Restricting multiple Login we can use Codeunit 40 - LogInManagement.

So let's see how we can achieve this -

1. Design Codeunit 40, Navigate to Function CompanyOpen().

2. Append Below Lines as below -

Before 
---------------------------------------------------
IF GUIALLOWED THEN
  LogInStart;
---------------------------------------------------

After
---------------------------------------------------
//>>Saurav.NAVBlog
ActiveSession.SETRANGE("User ID",USERID);
ActiveSession.SETRANGE("Client Type",ActiveSession."Client Type"::"Windows Client");
IF ActiveSession.COUNT > 1 THEN
  ERROR('You are Already Logined');
//<<Saurav.NAVBlog

IF GUIALLOWED THEN
  LogInStart;
---------------------------------------------------

Where - 
ActiveSession is of type Record Active Session



The Client Type have following Options -
Windows Client,SharePoint Client,Web Service,Client Service,NAS,Background,Management Client,Web Client,Unknown

Above Code will Stop Windows Client to use multiple session with same User ID.

Let's see how it executes -

I have successfully opened the first session with my User ID (as shown in background), when i tried to open the next session i got below listed error message.



I hope you find the post useful and let me know the feedback of such basic navision post on the Contact form or as a comment to post.

Stay tuned for More.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.