Page extension 6627 "FS Service Order Subform"
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · BC29-30 · source at ea08af5e · facts from BC29
Extends Service Order Subform.
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 |
|---|---|---|---|
| addlast(Control1) | Coupled to FS | Coupled to FS | Specifies if the entity is coupled to an entity in Field Service. |
Triggers
OnOpenPage
Relations
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 5330 “CRM Integration Management” (1 call:
OnOpenPage → IsCRMIntegrationEnabled)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "FS Service Order Subform"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.