BC Observatoryunofficial, made by waldo
tableRelationship Managementofficial - Microsoftderived - from the source, no model text

Table 7101 "Contact Sync Folder"

Base Application · Microsoft.CRM.Outlook

Open in Claude7101.mdSource on GitHub

Across versions

  1. BC23-27not present
  2. BC28added
  3. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Page 7030 "Folder Lookup" (pages and codeunits on it)Folder Lookup

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

Properties

Property Value
TableType Temporary
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 Entry No. Integer —
2 Folder ID Text[2048] —
3 Display Name Text[250] Select this folder
4 Parent Id Text[2048] — DataClassification SystemMetadata

Keys

  • PK: Entry No. (clustered)

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

Evidence 1 sources