pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 6713 "OData Fields Export"

Base Application · System.Integration

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 9750 "Web Service Management" (calls, 5 links)Web Service ManagementCodeunit 6710 "ODataUtility" (calls, 3 links)ODataUtilityCodeunit 1481 "Edit in Excel" (calls)Edit in Excel

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 · System.Integration · captioned “Select Fields to Export” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Select Fields to Export
PageType StandardDialog

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
Content Choose columns to export part Page 6710 “OData Column Choose SubForm” —

Procedures

  • SetExportData(var ExportTenantWebService: Record "Tenant Web Service"; var ExportRecRef: RecordRef)

Triggers

OnOpenPage, OnQueryClosePage

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.

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: "OData Fields Export"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources