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

Page extension 99000831 "Mfg. PurchDocumentLineEntity"

Base Application · Microsoft.Integration.Entity

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28-30unchanged

Neighbourhood 1 connected objects and pages

Page 6405 "Purchase Document Line Entity" (relates to)Purchase Document Line Entity

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.Integration.Entity · BC27-30 · source at ea08af5e · facts from BC29

Extends Purchase Document Line Entity.

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
addafter(returnsDeferralStartDate) prodOrderNumber Prod. Order No. —
addafter(subtype) routingNumber Routing No. —
operationNumber Operation No. —
workCenterNumber Work Center No. —
finished Finished —
prodOrderLineNumber Prod. Order Line No. —
addafter(safetyLeadTime) routingReferenceNumber Routing Reference No. —

Relations

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: "pageextension", object_name: "Mfg. PurchDocumentLineEntity"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources