Skip to main content

Client Management in Business Central using AL Code

Introduction:

Have you ever got into a requirement, where you are needed to actually execute the logic separately for different client types?

Well, this blog is just going to discuss the ClientType DataType and different ways of getting ClientTypes and how to use it in your code.


Pre-requisites:

  • Microsoft Dynamics Business Central Online
  • AL Language Extension
  • VS Code

References:

Demonstration:

ClientType:
In order to understand how to use ClientTypes, we need to understand what ClientTypes represents.
ClientType is an Option based DataType introduced in Business Central. That is in order to get the value or use the value we need to simply use just like ClientType::<Option Value>

ClientType has the following OptionMembers:
MemberDescription
BackgroundA background client.
ChildSessionA child session client.
DesktopA desktop client.
ManagementA management client.
NASA NAS client.
ODataA NAS client.
PhoneMicrosoft Dynamics Business Central Phone client.
SOAPA SOAP client.
TabletMicrosoft Dynamics Business Central Tablet client.
WebMicrosoft Dynamics Business Central Web client.
WindowsMicrosoft Dynamics Business Central Windows client.
CurrentMicrosoft Dynamics Business Central Windows client.
DefaultThe default client.
ODataV4A ODataV4 client.
ApiAn API client.


Applying ClientType:
In this code, I will explain how to select a specific Client Type in AL Code.
There are two ways of selecting the Client Type.
1. Using Client Type Management Codeunit: The syntax will be
    CU_ClientManagement.GetCurrentClientType

2. Using CurrentClientType function: Just like using 'CurrentCompany' standard function, you can use the CurrentClientType function

 trigger OnOpenPage();
    var
    CU_ClientManagement: Codeunit "Client Type Management";
    ClientType_1 : ClientType;
    begin
        Clear(CU_ClientManagement);
        If CU_ClientManagement.GetCurrentClientType() = ClientType_1::Api then begin 
            Message('API Client Type');
        end;

        If CurrentClientType = ClientType_1::Background then begin 
            Message('Background Client Type');
        end;

    end;
}

Conclusion:

In this blog, we covered what is ClientType DataType and how to use it to find what is the ClientType of the logged-in session.

I have personally discovered this datatype and found out the different ClientTypes that were added recently.

I hope this helps you get a clear understanding, implications, and how to apply it. :) 



Comments

  1. No need to create a ClientType_1 variable, Enum values can be directly accessed as Enums are static.


    trigger OnOpenPage();
    var
    CU_ClientManagement: Codeunit "Client Type Management";
    begin
    Clear(CU_ClientManagement);
    If CU_ClientManagement.GetCurrentClientType() = ClientType::Api then begin
    Message('API Client Type');
    end;

    If CurrentClientType = ClientType::Background then begin
    Message('Background Client Type');
    end;

    end;
    }

    ReplyDelete
  2. Thanks agreed.
    I also wanted to also demonstrate the datatype as well.

    ReplyDelete

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe