tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 140 "License Agreement"

Base Application · Microsoft

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC261 fields changed
  5. BC27-30unchanged

Neighbourhood 2 connected objects and pages

Page 180 "Additional Cust. Terms Setup" (pages and codeunits on it)Additional Cust. Terms SetupPage 181 "Additional Customer Terms" (pages and codeunits on it)Additional Customer Terms

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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption License Agreement
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 Primary Key Δ BC26 Code[10] —
2 Message for Accepting User Text[250] —
3 Effective Date Date —
4 Effective Date Changed By Text[65] — not editable; DataClassification EndUserIdentifiableInformation
5 Effective Date Changed On DateTime — not editable
6 Accepted Boolean Specifies if the license agreement was accepted. via Page 180 “Additional Cust. Terms Setup”
7 Accepted By Text[65] Specifies the person that accepted the license agreement. via Page 180 “Additional Cust. Terms Setup” not editable; DataClassification EndUserIdentifiableInformation
8 Accepted On DateTime Specifies the date the license agreement is accepted. via Page 180 “Additional Cust. Terms Setup” not editable

Keys

  • Key1: Primary Key (clustered)

Procedures

  • ShowEULA()
  • GetActive(): Boolean

Triggers

OnInsert

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: "License Agreement"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources