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

Table extension 30200 "Shpfy Feature Data Update"

Shopify · Microsoft.Integration.Shopify

Open in Claude30200.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Table 2610 "Feature Data Update Status" (relates to)Feature Data Update Status

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.

Shopify · Microsoft.Integration.Shopify · BC29-30 · source at ea08af5e · facts from BC29

Extends Feature Data Update Status.

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
30200 Shpfy Templates Migrate Boolean Migrate Shopify templates caption obsolete Removed 25.0; DataClassification SystemMetadata

Relations

Deprecations

  • object: guarded (#if not CLEANSCHEMA25)
  • field Shpfy Templates Migrate: Removed 25.0, “Not used anymore.”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "tableextension", object_name: "Shpfy Feature Data Update"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources