Codeunit 9108 "SharePoint Operation Response"

System Application · System.Integration.Sharepoint · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• GetResultAsText(var Result: Text) Δ BC24 (internal)
• GetResultAsStream(var ResultInStream: InStream) Δ BC24 (internal)
• SetHttpResponse(HttpResponseMessage: HttpResponseMessage) Δ BC24 Δ BC24 (internal)
• SetHttpResponse(ResponseContent: Text; ResponseHttpHeaders: HttpHeaders; ResponseHttpStatusCode: Integer; ResponseIsSuccessStatusCode: Boolean; ResponseReasonPhrase: Text) Δ BC24 Δ BC24 (internal)
• GetHeaderValueFromResponseHeaders(HeaderName: Text): Text Δ BC24 (internal)
• GetRetryAfterHeaderValue(): Integer Δ BC24 (internal)
• GetDiagnostics(): Interface "HTTP Diagnostics" Δ BC24 (internal)

Plus 2 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 4100 “Temp Blob” (3 calls: GetResultAsStream → CreateInStream, GetResultAsText → CreateInStream, SetHttpResponse → CreateOutStream)
• Codeunit 9111 “SharePoint Diagnostics” (1 call: SetHttpResponse → SetParameters)

Called by

• Codeunit 9101 “SharePoint Client Impl.” (38 calls: AddFileToFolder → GetDiagnostics, AddFileToFolder → GetResultAsText, CreateFolder → GetDiagnostics, …)

Recent changes

• 2026-07-14 #8742 Enhance SharePoint error handling and add tests (main, BC30, fix)

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