Codeunit 8754 "DA Feature Telemetry"

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

Properties

Procedures

• LogFeatureEnabled() (internal)
• LogFeatureDisabled() (internal)
• LogFeatureUsed() (internal)
• LogFileUploaded(DocumentAttachment: Record "Document Attachment") (internal)
• LogFileDownloaded(DocumentAttachment: Record "Document Attachment") (internal)
• LogFileDownloadFailed(DocumentAttachment: Record "Document Attachment"; ErrorText: Text; ErrorCallStack: Text) (internal)
• LogFileDeleted(DocumentAttachment: Record "Document Attachment") (internal)
• LogCompanyMigration() (internal)
• LogManualSync() (internal)
• LogAutoSync() (internal)
• LogRootFolderConfigured() (internal)

Plus 3 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 8703 “Feature Telemetry” (11 calls: LogAutoSync → LogUsage, LogCompanyMigration → LogUsage, LogFeatureDisabled → LogUptake, …)

Called by

• Codeunit 8751 “DA External Storage Impl.” (7 calls: DeleteExternalFile → LogFileDeleted, DocumentAttachment_OnBeforeExportToStream → LogFileDownloadFailed, DocumentAttachment_OnBeforeGetAsTempBlob → LogFileDownloadFailed, …)
• Report 8752 “DA External Storage Sync” (2 calls: LogSyncTelemetry → LogAutoSync, LogSyncTelemetry → LogManualSync)
• Report 8753 “DA External Storage Migration” (1 call: LogMigrationTelemetry → LogCompanyMigration)

Recent changes

• 2026-09-15 #10828 Avoid remote attachment checks during FactBox refresh (main, BC30, performance)

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