Page extension 6623 "FS Location List"

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · BC29-30 · source at ea08af5e · facts from BC29

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 project task is coupled to an entity in Field Service.

Actions

Group	Action	ToolTip
Dynamics 365 Field Service	Warehouse in Field Service	Open the coupled Dynamics 365 Field Service entity.
	Synchronize	Send updated data to Dynamics 365 Field Service.
Coupling	Set Up Coupling	Create or modify the coupling to a Dynamics 365 Field Service product.
	Delete Coupling	Delete the coupling to a Dynamics 365 Field Service entity.
Dynamics 365 Field Service	Synchronization Log	View integration synchronization jobs for the location table.

Triggers

OnAfterGetCurrRecord, OnOpenPage

Relations

extends Page 15 “Location List”

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)
Codeunit 5331 “CRM Coupling Management” (1 call: OnAfterGetCurrRecord → IsRecordCoupledToCRM)

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