BC Observatoryunofficial, made by waldo
reportPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Report 8752 "DA External Storage Sync"

External Storage - Document Attachments · Microsoft.ExternalStorage.DocumentAttachments

Open in Claude8752.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Codeunit 8754 "DA Feature Telemetry" (calls, 2 links)DA Feature Telemetry

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.

External Storage - Document Attachments · Microsoft.ExternalStorage.DocumentAttachments · captioned “External Storage Synchronization” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption External Storage Synchronization
Extensible false
UsageCategory None
ApplicationArea All
Permissions tabledata “DA External Storage Setup” = r, tabledata “Document Attachment” = r

Procedures

2 local procedures, no public ones.

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: "report", object_name: "DA External Storage Sync"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources