Report.DefaultLayout(Integer) Method
Version: Available or changed with runtime version 1.0.
Gets the default built-in layout type that is used on a specified report.
Syntax
DefaultLayout := Report.DefaultLayout(Number: Integer)
Parameters
Number
Type: Integer
The ID of the report that you want to save. If the report that you specify does not exist, then a run-time error occurs.
Return Value
DefaultLayout
Type: DefaultLayout
The default built-in layout type that is used on a specified report.
Remarks
The default layout for a report is specified by the report's DefaultLayout Property.
Example (using Report::<object identifier>
syntax)
As mentioned above, the Report.DefaultLayout
method will throw a run-time error if no report with the supplied object ID exists. If you know the report object, a safe way to call Report.DefaultLayout is to use the Report::<object identifier>
syntax as the compiler will tell you if Report1 doesn't exist.
procedure MyProcKnownReport()
var
layout: DefaultLayout;
begin
// When you know the report object, this is safe
// as the compiler will tell you if MyReport does not exist
layout := Report.DefaultLayout(Report::MyReport);
end;
Example (using a Try function)
As mentioned above, the Report.DefaultLayout
method will throw a run-time error if no report with the supplied object ID exists. If you don't know the report object in your AL code, then you can wrap the Report.DefaultLayout
method in a Try function as it doesn't write to the database.
procedure GetLayout(ObjectId: Integer): DefaultLayout
var
layout: DefaultLayout;
begin
if not TryReportDefaultLayout(ObjectId) then begin
// handle error here
end
else // now it's safe to call Report.DefaultLayout
layout := Report.DefaultLayout(ObjectId);
exit(layout);
end;
[TryFunction]
// Safe to wrap Report.DefaultLayout in a Try function
// as it doesn't write to the database
procedure TryReportDefaultLayout(ObjectId: Integer)
var
layout: DefaultLayout;
begin
layout := Report.DefaultLayout(ObjectId);
end;
See also
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour