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

Table 5466 "API Entities Setup"

Base Application · Microsoft.API

Open in Claude5466.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-28unchanged
  4. BC291 fields changed
  5. BC30unchanged

Neighbourhood 2 connected objects and pages

Table 232 "Gen. Journal Batch" (relates to)Gen. Journal BatchPage 1876 "Integration Services Setup" (pages and codeunits on it)Integration Services Setup

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.

Base Application · Microsoft.API · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption API Entities Setup
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 PrimaryKey Code[20] —
3 Customer Payments Batch Name Δ BC29 Code[10] Specifies the default customer payments batch name of the integration journal. TableRelation Table 232 “Gen. Journal Batch” (“Gen. Journal Batch”.Name where(“Journal Template Name” = const(‘CASHRCPT’)))
4 Demo Company API Initialized Boolean —

Keys

  • Key1: PrimaryKey (clustered)

Procedures

  • SafeGet()

Triggers

OnInsert

Relations

Pages and codeunits on this table

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: "table", object_name: "API Entities Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources