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

Page 6105 "Inbound E-Documents"

EDocument · Microsoft.eServices.EDocument

Across versions

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

Neighbourhood 2 connected objects and pages

Table 6121 "E-Document" (relates to)E-DocumentCodeunit 3303 "Payables Agent" (event subscribers)Payables Agent

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
Extensible false
SourceTable E-Document
PageType List
UsageCategory Lists
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
DocumentList Entry No. Entry No Specifies the unique number of the document.
Document DocumentNameTxt Specifies the unique name for the document.
Vendor Name ConfirmedVendorTxt Specifies the bill-to/pay-to name of the document that was confirmed by the user during processing.
Processing Status Import Processing Status Specifies the stage in which the processing of this document is in.
Document Date Document Date Specifies the date of the document.
Due Date Due Date Specifies the due date of the document.
Agent Task No. AgentTask.ID Specifies the task number for the document.
Task Status obsolete Pending 28.0; #if not CLEAN28 AgentTask.Status Specifies the status of the agent task for this document.
Agent Task Status AgentTaskStatus Specifies the status of the agent task for this document.
Sender obsolete Pending 29.0; #if not CLEAN29 EDocumentPurchaseHeader."Vendor Company Name" Specifies the vendor name of the document.
Sender SenderNameTxt Specifies the sender name of the document.
Received At Rec.SystemCreatedAt Specifies the date and time when the document was created.
Service Service Specifies the E-Document Service that retrieved the document.
Source Service Integration Specifies the source of the document.
Source Details Source Details Specifies the details about the source of the document.
Document Type Document Type Specifies the type of the document.
Finalized Document No. RecordLinkTxt Specifies the entity created from the document.
FactBoxes Documents part Page 1178 “Doc. Attachment List Factbox” —
Preview part Page 6111 “Inbound E-Doc. Picture” —
E-Document Details part Page 6108 “Inbound E-Doc. Factbox” —
Messages part Page 6434 “E-Document Messages FactBox” —

Actions

Group Action ToolTip Runs
Processing Import PDF Create an electronic document by importing a PDF file.
Import XML Create an electronic document by importing an XML file.
Import other file Create an electronic document by manually uploading a file.
View e-mail message obsolete Pending 27.0; #if not CLEAN27 View the source e-mail message.
Analyze PDF Analyze the pdf document with Azure Document Intelligence.
Prepare Draft Prepare the draft document.
Open draft document Process the selected document.
E-Document Services Opens E-Document Services page. Page 6103 “E-Document Services”
E-Document Logs Opens E-Document Logs page. Page 6125 “E-Document Logs”
View source file View the source file.
Download file Download the source file.

Trigger event subscribers

Procedures

  • ProcessFilesUploads(EDocumentService: Record "E-Document Service"; Files: List of [FileUpload]; Type: Enum "E-Doc. File Format") (internal)

Plus 11 local procedures.

Triggers

OnAfterGetRecord

Relations

Recent changes

Deprecations

  • procedure SetEmailActionsVisibility: guarded (#if not CLEAN27)

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

Evidence 1 sources