---
id: object/pageextension/6614
type: object
title: Page extension 6614 "FS Service Order"
summary: Page extension 6614 "FS Service Order" in FieldServiceIntegration (Microsoft.Integration.DynamicsFieldService), extends "Service Order". Introduced in BC29, still in BC30.
tier: official
language: en
tags:
  - pageextension
  - fieldserviceintegration
versions:
  introduced: "29"
  last_changed: null
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: ec3017cf6b6378ebf1052200b2060f9446a5449e656c79001825c47e058eefcb
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Apps/W1/FieldServiceIntegration/app/src/Page%20Extensions/FSServiceOrder.PageExt.al
    title: src/Apps/W1/FieldServiceIntegration/app/src/Page Extensions/FSServiceOrder.PageExt.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects:
    - object/page/5900
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: pageextension
object_id: 6614
name: FS Service Order
namespace: Microsoft.Integration.DynamicsFieldService
app: FieldServiceIntegration
extends: Service Order
first_version: "29"
last_version: "30"
present_in:
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 0
  events: 0
  subscribers: 0
  controls: 1
  actions: 6
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 2
  called_by: 0
  implements: 0
---

# Page extension 6614 "FS Service Order"

> Page extension 6614 "FS Service Order" in FieldServiceIntegration (Microsoft.Integration.DynamicsFieldService), extends "Service Order". Introduced in BC29, still in BC30.

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · BC29-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Apps/W1/FieldServiceIntegration/app/src/Page%20Extensions/FSServiceOrder.PageExt.al) · facts from BC29

Extends [Service Order](../page/5900.md).

## 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 |
|---|---|---|---|
| modify(Service Order Type) | Service Order Type | modifies `Service Order Type` | — |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Dynamics 365 Field Service | Work Order | Open the coupled Dynamics 365 Field Service record. |  |
|  | Synchronize | Send updated data to Dynamics 365 Field Service. |  |
| Coupling | Set Up Coupling | Create or modify the coupling to a Dynamics 365 Field Service record. |  |
|  | Match-Based Coupling | Couple service orders to work orders in Dynamics 365 Field Service record based on matching criteria. |  |
|  | Delete Coupling | Delete the coupling to a Dynamics 365 Field Service record. |  |
| Dynamics 365 Field Service | Synchronization Log | View integration synchronization jobs for the resource table. |  |

## Triggers

OnAfterGetCurrRecord, OnOpenPage

## Relations

- extends [Page 5900 "Service Order"](../page/5900.md)

## 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"](../codeunit/5330.md) (1 call: `OnOpenPage → IsCRMIntegrationEnabled`)
- [Codeunit 5331 "CRM Coupling Management"](../codeunit/5331.md) (1 call: `OnAfterGetCurrRecord → IsRecordCoupledToCRM`)

## Across versions

- Present in: BC29-30
- Changed (declaration) in: none

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## 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")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.