Codeunit 6615 "FS Integration Mgt."
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 9 connected objects and pages
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · BC29-30 · source at ea08af5e · facts from BC29
Events published
OnGetBookingStatusCompletedOnSetFilterForFSBookingStatus(var FSBookingStatus: Record "FS Booking Status")(integration)
Event subscriptions
- RegisterFSConnectionOnRegisterServiceConnection subscribes to Table “Service Connection” OnRegisterServiceConnection
Procedures
ImportFSSolution(ServerAddress: Text; IntegrationUserEmail: Text; AdminUserEmail: Text; AdminUserPassword: SecretText; AccessToken: SecretText; AdminADDomain: Text; ProxyVersion: Integer; ForceRedeploy: Boolean; ImportSolutionFailed: Boolean)(internal)IsFSSolutionInstalled(): Boolean(internal)EnableServiceOrderArchive()(internal)TestManualServiceOrderNoSeriesFlag(IntegrationType: Enum "FS Integration Type")(internal)SetServiceOrderNoSeriesToManual(ErrorInfo: ErrorInfo)TestOneServiceItemLinePerOrder(IntegrationType: Enum "FS Integration Type")(internal)TestOneServiceItemLinePerOrderModificationIsAllowed(ServiceMgtSetup: Record "Service Mgt. Setup")(internal)GetDefaultWorkOrderIncident(): Guid(internal)GenerateDefaultWorkOrderIncident(): Guid(internal)GetBookingStatusCompleted(): Guid(internal)ReturnIntegrationTypeLabel(FSConnectionSetup: Record "FS Connection Setup"): Text(internal)
Plus 10 local procedures.
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 7201 “CDS Integration Impl.” (10 calls:
ImportFSSolution → ActivateConnection,ImportFSSolution → AssignTeamRole,ImportFSSolution → GetAuthenticationTypeToken, …) - Codeunit 5330 “CRM Integration Management” (9 calls:
ImportFieldServiceIntegrationSolution → IsSolutionOutdated,ImportFieldServiceIntegrationSolution → ProcessConnectionFailures,ImportFSSolution → CheckConnectRequiredFields, …) - Codeunit 5344 “CRM Product Name” (1 call:
ImportFSSolution → CDSServiceName) - Page 456 “No. Series” (1 call:
TestManualServiceOrderNoSeriesFlag → (object))
Called by
- Codeunit 6610 “FS Int. Table Subscriber” (4 calls:
HandleOnBeforeInsertRecord → GetDefaultWorkOrderIncident,LogTelemetryOnAfterInitSynchJob → ReturnIntegrationTypeLabel,ResetServiceOrderLineFromFSBookableResourceBooking → GetBookingStatusCompleted, …) - Table 6623 “FS Connection Setup” (4 calls:
DeployFSSolution → ImportFSSolution,DeployFSSolution → IsFSSolutionInstalled,InstallIntegrationSolution → ImportFSSolution, …) - Codeunit 6611 “FS Setup Defaults” (3 calls:
ResetConfiguration → EnableServiceOrderArchive,ResetConfiguration → GenerateDefaultWorkOrderIncident,ResetServiceOrderLineResourceMapping → GetBookingStatusCompleted) - Page 6613 “FS Connection Setup Wizard” (2 calls:
FinalizeSetup → ImportFSSolution,OnOpenPage → ReturnIntegrationTypeLabel) - Page 6612 “FS Connection Setup” (1 call:
OnOpenPage → ReturnIntegrationTypeLabel)
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: "codeunit", object_name: "FS Integration Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.