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

Table 6106 "E-Doc. Import Parameters"

EDocument · Microsoft.EServices.EDocument.Processing.Import

Across versions

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

EDocument · Microsoft.EServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableType Temporary

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
2 Processing Customizations Enum “E-Doc. Proc. Customizations” — enum Enum 6110 “E-Doc. Proc. Customizations”
5 Step to Run / Desired Status Option —
1 Step to Run Enum “Import E-Document Steps” — enum Enum 6114 “Import E-Document Steps”
6 Desired E-Document Status Enum “Import E-Doc. Proc. Status” — enum Enum 6100 “Import E-Doc. Proc. Status”
3 Purch. Journal V1 Behavior Option —
4 Create Document V1 Behavior Boolean —
10 Existing Doc. RecordId RecordId —

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: "table", object_name: "E-Doc. Import Parameters"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources