For example:-

codeunit 50101 “Test Functions”

{

procedure Factorial()

var

IntValue, IntValue2, Fact : Integer;

begin

IntValue := 5;

IntValue2 := IntValue;

Fact := 1;

while

IntValue >= 1

do begin

Fact := Fact * IntValue;

IntValue -= 1;

end;

Message(‘IntValue = %2, My Factorial value is %1’, Fact, IntValue2);

end;

}

• The next step is to decide in which page we should see our desired result
• So we will create a ‘page extension’ for that page using snipper ‘tpageext’
• Inside the action section we give our action a name and call our code unit using a trigger

For example :-

pageextension 50101 CustomerListExt extends “Item List”

{

layout

{

// Add changes to page layout here

}

actions

{

addlast(Functions)

{

action(Factorial)

{

ApplicationArea = All;

Caption = ‘Factorial’;

trigger OnAction()

var

TestFunctionCodeunit: Codeunit “Test Functions”;

begin

// TestFunctionCodeunit.Run();

TestFunctionCodeunit.Factorial();

end;

}

}

After this, we should publish our program and check for the result

Advantages of CodeUnit :-

• CodeUnit is the best way for creating procedures
• We can simply call those codeunits wherever we wish in our program and this help in reusability.