BC Observatoryunofficial, made by waldo
pageextensionSales & Receivablesofficial - Microsoftderived - from the source, no model text

Page extension 8056 "Vendor Card"

Subscription Billing · Microsoft.SubscriptionBilling

Open in Claude8056.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Page 26 "Vendor Card" (relates to)Vendor Card

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.

Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29

Extends Vendor Card.

Actions

Group Action ToolTip Runs
addlast(creation) Subscription Contract Create a Subscription Contract for the vendor. Page 8070 “Vendor Contract”
addlast(Vendor) Subscription Contracts View a list of ongoing Vendor Subscription Contracts. Page 8071 “Vendor Contracts”

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "pageextension", object_name: "Vendor Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources