Codeunit 9109 "SharePoint Request Helper"
System Application · System.Integration.Sharepoint
Across versions
- BC23present
- BC243 procedures changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
System Application · System.Integration.Sharepoint · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Events published
OnBeforeSendRequest(HttpRequestMessage: HttpRequestMessage; var SharePointOperationResponse: Codeunit "SharePoint Operation Response"; var IsHandled: Boolean; Method: Text)(internal)
Procedures
SetAuthorization(Auth: Interface "SharePoint Authorization")Get(SharePointUriBuilder: Codeunit "SharePoint Uri Builder"): Codeunit "SharePoint Operation Response"Post(SharePointUriBuilder: Codeunit "SharePoint Uri Builder"): Codeunit "SharePoint Operation Response"Post(SharePointUriBuilder: Codeunit "SharePoint Uri Builder"; SharePointHttpContent: Codeunit "SharePoint Http Content"): Codeunit "SharePoint Operation Response"Patch(SharePointUriBuilder: Codeunit "SharePoint Uri Builder"; SharePointHttpContent: Codeunit "SharePoint Http Content"): Codeunit "SharePoint Operation Response"Delete(SharePointUriBuilder: Codeunit "SharePoint Uri Builder"): Codeunit "SharePoint Operation Response"
Plus 4 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 9110 “SharePoint Uri Builder” (1 call:
PrepareRequestMsg → GetUri)
Called by
- Codeunit 9101 “SharePoint Client Impl.” (42 calls:
AddFileToFolder → Post,AddFileToFolder → SetAuthorization,CreateFolder → Post, …)
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 Request Helper"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.