Page 9666 "Report Theme and Header/Footer"
Base Application · Microsoft.Foundation.Reporting
Across versions
- BC23-28not present
- BC29added
- BC30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Foundation.Reporting · captioned “Manage themes and header-footer layouts” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Manage themes and header-footer layouts |
| Extensible | true |
| SourceTable | Report Layout List |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | Layout Name | Rec."Caption" |
Specifies the friendly, translated display name of the theme or header/footer part. For tenant-defined parts this matches the name. |
| Name | Rec.Name |
Specifies the name that identifies the theme or header/footer part. This is the value stored when the part is assigned to a report. | |
| Description | Rec.Description |
Specifies the description of the theme or header/footer part. | |
| Type | Rec."Layout Subtype" |
Specifies whether the artifact is a Theme or a Header/Footer part. | |
| Publisher | Rec."Layout Publisher" |
Specifies the extension and publisher that owns the artifact. Empty for tenant-defined parts. | |
| Status | Rec."Layout Status" |
Specifies the lifecycle status of the artifact. New parts start as Draft; only Approved parts can be assigned as report defaults. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | New theme | Upload a new theme part. | |
| New header/footer | Upload a new header/footer part. | ||
| Export | Export the selected artifact file. | ||
| Show info | Show details of the selected theme or header/footer part, including how many report configurations currently use it. | ||
| Edit description | Edit the description of the selected tenant-defined theme or header/footer part. Out-of-box parts cannot be edited. | ||
| Replace | Replace the layout file of the selected tenant-defined theme or header/footer part. Out-of-box parts cannot be replaced. | ||
| Delete | Delete the selected tenant-defined artifact. Out-of-box parts cannot be deleted. | ||
| Part Status | Set as Approved | Approve the selected parts so they can be assigned as report defaults. | |
| Set as Draft | Move the selected parts back to Draft. Draft parts cannot be assigned as report defaults. | ||
| Set as Pending Approval | Mark the selected parts as pending approval. | ||
| Set as Retired | Retire the selected parts so they are no longer offered for assignment. |
Procedures
SetLookupSubtype(Subtype: Enum "Report Layout Subtype")(internal)
Plus 9 local procedures.
Triggers
OnOpenPage
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 9665 “Composite Layout Lookup Helper” (6 calls:
CountAssignedInSelection → CountPartAssignments,CreateArtifact → GetTenantReportDefaultsReportID,DeleteSelectedArtifact → ClearPartAssignments, …) - Codeunit 9660 “Report Layouts Impl.” (5 calls:
CreateArtifact → InsertNewLayout,DeleteSelectedArtifact → DeleteReportLayout,EditPartDescription → UpdateReportLayoutDescription, …) - Codeunit 265 “Feature Key Management” (1 call:
OnOpenPage → IsDocumentReportExperienceEnabled)
Recent changes
- 2026-09-10 #11211 [Bug 649379] Composite layout stress-test fixes, part resolution source and status action captions (main, BC30, fix)
- 2026-08-21 #10134 [Bug 646487] Composite layout: focus fix, body-layout gating, and setup UI (main, BC30, fix)
- 2026-08-10 #9949 [Bug 645022] UI improvements for report themes and header/footers (composite layout) (main, BC30, feature)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Report Theme and Header/Footer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.