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

Page 7606 "Customized Calendar Entries"

Base Application · Microsoft.Foundation.Calendar

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 7603 "Customized Calendar Entry" (relates to)Customized Calendar EntryCodeunit 7600 "Calendar Management" (calls)Calendar Management

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 Customized Calendar Entries
SourceTable Customized Calendar Entry
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 Source Type Source Type Specifies whether this customized calendar entry was set up for your company, a customer, vendor, location, shipping agent, or a service. from the table field
Base Calendar Code Base Calendar Code Specifies which base calendar was used as the basis for this customized calendar. from the table field
Content CustomizedCalendarEntries part Page 7605 “Customized Cal. Entries Subfm” —

Actions

Group Action ToolTip Runs
Functions Maintain Customized Calendar Changes View or edit a customized calendar. You would typically enter any nonworking days that you want to apply to a 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 7603 “Customized Calendar Changes”

Triggers

OnAfterGetRecord

Relations

Called by

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.

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

Evidence 1 sources