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

Page 6103 "E-Document Services"

EDocument · Microsoft.eServices.EDocument

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 11 connected objects and pages

Table 6103 "E-Document Service" (relates to)E-Document ServiceTable 6103 "E-Document Service" (pages and codeunits on it, 2 links)E-Document ServicePage 6133 "E-Document Service" (pages and codeunits on it)E-Document ServiceElectronic invoicing in Norway (Learn pages)Electronic invoicing in NorwayExtending the e-documents functionality (Learn pages)Extending the e-documents fu…Match Purchase Invoice Drafts to Purchase Orders (Learn pages)Match Purchase Invoice Draft…Set Up E-documents (Learn pages)Set Up E-documentsSet up electronic invoicing with NemHandel (Learn pages)Set up electronic invoicing …Set up the E-Documents connector with external endpoints (Learn pages)Set up the E-Documents conne…Use e-documents in sales (Learn pages)Use e-documents in salesUse E-Documents in the purchase process (Learn pages)

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.

EDocument · Microsoft.eServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption E-Document Services
SourceTable E-Document Service
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
General Code Code Specifies the code of the electronic export setup.
Description Description Specifies the description of the electronic export setup.
Export Format Document Format Specifies the export format of the electronic export setup.
Service Integration Service Integration V2 Specifies service integration for the electronic document setup.
Service Integration (Legacy) obsolete Pending 26.0; #if not CLEAN26 Service Integration Specifies service integration for the electronic document setup.

Actions

Group Action ToolTip Runs
Retention Policy E-Document Log View or edit the retention policy. Page 3901 “Retention Policy Setup Card”
E-Document Integration Log View or edit the retention policy. Page 3901 “Retention Policy Setup Card”
E-Document Mapping Log View or edit the retention policy. Page 3901 “Retention Policy Setup Card”
E-Document Data storage View or edit the retention policy. Page 3901 “Retention Policy Setup Card”
Data Exchange Reset Data Exch. Formats Reset E-Document provided Data Exch. Formats
Configure additional fields Configure the additional fields to consider when importing an E-Document.
Navigation Install E-Document integrations from AppSource Open AppSource to install services.

Triggers

OnOpenPage

Relations

Pages and codeunits on this table

Recent changes

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: "E-Document Services"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 8 of 9 sources

Show 1 more