codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6613 "FS Assisted Setup Subscriber"

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 5 connected objects and pages

Codeunit 1990 "Guided Experience" (calls, 3 links)Guided ExperienceCodeunit 43 "Language" (calls)LanguageCodeunit 5344 "CRM Product Name" (calls)CRM Product NameCodeunit 9179 "Application Area Mgmt. Facade" (calls)Application Area Mgmt. FacadePage extension 6622 "FS Service Connections" (calls)FS Service Connections

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Event subscriptions

  • RegisterFSAssistedSetup subscribes to Codeunit “Guided Experience” OnRegisterAssistedSetup

Procedures

  • RegisterAssistedSetup() (internal)

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.

Called by

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

Evidence 1 sources