codeunitAdministration & Setupofficial - Microsoftderived - from the source, no model text

Codeunit 4014 "Notification Handler"

HybridBaseDeployment · Microsoft.DataMigration

Across versions

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

Neighbourhood 8 connected objects and pages

Codeunit 4008 "Hybrid BC Management" (event subscribers)Hybrid BC ManagementCodeunit 4021 "Hybrid BC Last Management" (event subscribers)Hybrid BC Last ManagementCodeunit 4001 "Hybrid Cloud Management" (calls, 10 links)Hybrid Cloud ManagementCodeunit 5459 "JSON Management" (calls, 10 links)JSON ManagementCodeunit 4011 "Hybrid Message Management" (calls, 3 links)Hybrid Message ManagementCodeunit 6060 "Hybrid Deployment" (calls, 2 links)Hybrid DeploymentCodeunit 5302 "Outlook Synch. Type Conv" (calls)Outlook Synch. Type ConvCodeunit 8714 "Audit Log" (calls)Audit Log

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.

HybridBaseDeployment · Microsoft.DataMigration · BC29-30 · source at ea08af5e · facts from BC29

Events published

Event subscriptions

  • HandleIntelligentCloudOnInsertWebhookNotification subscribes to Table “Webhook Notification” OnAfterInsertEvent

Procedures

  • ParseReplicationSummary(var HybridReplicationSummary: Record "Hybrid Replication Summary"; NotificationText: Text)
  • CheckForWarnings(HybridReplicationSummary: Record "Hybrid Replication Summary") (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.

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

Evidence 1 sources