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

Table 7121 "Contact Sync User"

Base Application · Microsoft.CRM.Outlook

Across versions

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

Neighbourhood 2 connected objects and pages

Codeunit 7100 "Contact Sync User Subscriber" (event subscribers, 2 links)Contact Sync User SubscriberCodeunit 3060 "Uri" (calls)Uri

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
Caption Contact Sync User
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 ID Integer — AutoIncrement; DataClassification SystemMetadata
2 User ID Code[50] — TableRelation User.“User Name”; NotBlank; DataClassification EndUserIdentifiableInformation
3 Last Sync Date Time DateTime — not editable; DataClassification SystemMetadata
4 Folder ID Text[250] — DataClassification SystemMetadata
5 Delta Url Text[2048] Delta URL caption DataClassification SystemMetadata
6 Folder Name Text[250] — DataClassification SystemMetadata

Keys

  • PK: ID (clustered)
  • UserFolder: User ID, Folder ID
  • FolderEmail: Folder ID
  • UserFolderSync: User ID, Folder ID, Last Sync Date Time

Trigger event subscribers

Procedures

  • SetDeltaUrl(NewDeltaUrl: Text)
  • GetDeltaUrl(): Text
  • EnforceRecordOwnership() (internal)
  • EnforceRecordOwnershipOnModify(OriginalUserId: Code[50]) (internal)
  • ValidateApprovedGraphDeltaUrl(DeltaUrlToValidate: Text): Boolean (internal)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Recent changes

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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 User"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources