pagePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Page 7600 "Base Calendar Card"

Base Application · Microsoft.Foundation.Calendar

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 7600 "Base Calendar" (relates to)Base CalendarPage 7601 "Base Calendar List" (pages and codeunits on it)Base Calendar ListSet up base calendars (Learn pages)Set up base calendars

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Foundation.Calendar · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Base Calendar Card
SourceTable Base Calendar
PageType ListPlus

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
General Code Code Specifies a code for the base calendar you are setting up.
Name Name Specifies the name of the base calendar in the entry. from the table field
Customized Changes Exist format(Rec."Customized Changes Exist") Specifies that the base calendar has been used to create customized calendars.
Content BaseCalendarEntries part Page 7604 “Base Calendar Entries Subform” —

Actions

Group Action ToolTip Runs
Base Calendar Where-Used List View a list of the BOMs that the selected items are components of.
Functions Maintain Base Calendar Changes View or edit a base calendar. You would typically enter any nonworking days that you want to apply to a base calendar that you are setting up, to change their status from working to nonworking. You can also use this window to edit a base calendar that has already been set up. Page 7602 “Base Calendar Changes”

Triggers

OnAfterGetRecord

Relations

Pages and codeunits on this table

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). 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: "Base Calendar Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources