Page 6615 "FS Work Order Types"
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · captioned “Work Order Types - Dynamics 365 Field Service” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Work Order Types - Dynamics 365 Field Service |
| SourceTable | FS Work Order Type |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Service |
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 |
|---|---|---|---|
| General | Code | Code | Specifies the work order type code. |
| Name | Name | Specifies the work order type name. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Create in Business Central | Generate the entity from the Field Service work order. | |
| Hide Coupled Records | Do not show coupled records. | ||
| Show Coupled Records | Show coupled records. |
Procedures
SetCurrentlyCoupledFSWorkOrderType(FSWorkOrderType: Record "FS Work Order Type")
Triggers
OnInit, OnOpenPage, OnAfterGetRecord
Relations
- source table Table 6622 “FS Work Order Type”
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:
OnInit → (object)) - Codeunit 5332 “Lookup CRM Tables” (1 call:
OnOpenPage → GetIntegrationTableMappingView) - Codeunit 9179 “Application Area Mgmt. Facade” (1 call:
OnOpenPage → IsPremiumExperienceEnabled)
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: "page", object_name: "FS Work Order Types"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.