BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 9102 "SharePoint List Item Atch."

System Application · System.Integration.Sharepoint

Open in Claude9102.mdSource on GitHub

Across versions

  1. BC23present
  2. BC245 procedures changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 9101 "SharePoint Client Impl." (calls, 2 links)SharePoint Client Impl.

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.

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

Properties

Property Value
Access Internal

Procedures

  • Parse(Payload: Text; var SharePointListItemAtch: Record "SharePoint List Item Atch" temporary) Δ BC24 Δ BC24
  • Parse(Payload: JsonObject; var SharePointListItemAtch: Record "SharePoint List Item Atch" temporary) Δ BC24 Δ BC24
  • ParseSingleReturnValue(Payload: Text; var SharePointListItemAtch: Record "SharePoint List Item Atch" temporary) Δ BC24
  • ParseSingle(Payload: Text; var SharePointListItemAtch: Record "SharePoint List Item Atch" temporary) Δ BC24 Δ BC24

Plus 1 local procedures.

Called by

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

Evidence 1 sources