tableRelationship Managementofficial - Microsoftderived - from the source, no model text

Table 5073 "Campaign Status"

Base Application · Microsoft.CRM.Campaign

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC282 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Page 5090 "Campaign Status" (pages and codeunits on it, 2 links)Campaign StatusTable 5071 "Campaign" (referenced by)Campaign

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

Properties

Property Value
Caption Campaign Status
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 Code Δ BC28 Code[10] Specifies the code for the campaign status. NotBlank
2 Description Δ BC28 Text[100] Specifies the description of the campaign status.

Keys

  • Key1: Code (clustered)

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

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

Evidence 1 sources