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

Table 5329 "CRM Redirect"

Base Application · Microsoft.Integration.Dataverse

Open in Claude5329.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Table 18 "Customer" (relates to)CustomerPage 5329 "CRM Redirect" (pages and codeunits on it)CRM Redirect

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

Properties

Property Value
Caption CRM Redirect
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 No. Code[10] —
2 Filter Text[128] — FlowField: lookup(Customer.Name)

Keys

  • Key1: No. (clustered)

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

Evidence 1 sources