tableextensionFinanceofficial - Microsoftderived - from the source, no model text

Table extension 20104 "AMC Bank Paym. Method Ext"

AMCBanking365Fundamentals · Microsoft.Bank.Payment

Across versions

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

Neighbourhood 2 connected objects and pages

Table 20102 "AMC Bank Pmt. Type" (relates to)AMC Bank Pmt. TypeTable 289 "Payment Method" (relates to)Payment Method

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.

AMCBanking365Fundamentals · Microsoft.Bank.Payment · BC29-30 · source at ea08af5e · facts from BC29

Extends Payment Method.

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
20100 AMC Bank Pmt. Type Text[50] Specifies the payment type that the AMC Banking 365 Fundamentals extension requires when you export payments that have the selected payment method. via Page extension 20104 “AMC Bank Paym. Meth. Page Ext” obsolete Pending 28.0; TableRelation Table 20102 “AMC Bank Pmt. Type” (AMC Bank Pmt. Type); DataClassification CustomerContent

Relations

Deprecations

  • object: guarded (#if not CLEANSCHEMA31)
  • field AMC Bank Pmt. Type: Pending 28.0, “AMC Banking 365 Fundamental extension is discontinued”

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: "AMC Bank Paym. Method Ext"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources