73
Hi all,
I'm working through different filed methods and came across the documentation highlighting two different validation options for fields in AL, TestField, and Validate
What are the differences between using these two, and which scenarios work best for each case?
It seems both can see if a record exists or doesn't have a value.
You can also check to see if a record meets criteria with seemingly the same syntax?
Hi, just adding some info.
In fact, there is Record.FieldError(Any [, String]) Method, you can also try.
Record.FieldError(Any [, String]) Method - Business Central | Microsoft Learn
Hope this helps as well.
Thanks.
ZHU
TestField and Validate are two different things.
TestField is to test whether the value of the field is what you want. On your example: Testing if the Customer Salesperson Code is ZX. If it is not ZX, it will throw an error.
Validation runs any validation logic on the OnValidate trigger of the field. If there is nothing on OnValidate trigger, there will be no error. In general, you should always runs the Validation.
You can have testfield inside OnValidate trigger. Example:
Customer.Validate("Phone No.", '1234567891234');
field(9; "Phone No."; Text[30])
{
trigger OnValidate()
begin
if Rec."Phone No." <> '' then
Rec.TestField("Salesperson Code",'ZX'); //meaning that you can only input Phone No if Salesperson is ZX
end;
}
TestField reference.
learn.microsoft.com/.../testfield-function--record-
Validate reference.
#1
YUN ZHU
448
Super User 2025 Season 1
#2
Sagar Dangar, MCP
358
#3
Mansi Soni
327
Share
Report
All responses (
Answers (
