BC Observatoryunofficial, made by waldo
enumPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Enum 61 "Electronic Document Format Usage"

Base Application · Microsoft.Foundation.Reporting

Open in Claude61.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25declaration changed
  4. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Enum extension 6464 "Serv. Electr.Doc.Format Usage" (extended by)Serv. Electr.Doc.Format Usage

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.Reporting · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible true

Values

Ordinal Name Caption Notes
0 Sales Invoice Sales Invoice
1 Sales Credit Memo Sales Credit Memo
2 Sales Validation Sales Validation
6 Job Quote Project Quote
7 Job Task Quote Project Task Quote

Extended by

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: "enum", object_name: "Electronic Document Format Usage"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources