tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 5370 "CRM Synch. Job Status Cue"

Base Application · Microsoft.Integration.Dataverse

Across versions

  1. BC23present
  2. BC241 fields changed
  3. BC25-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryPage 5371 "CRM Synch. Job Status Part" (pages and codeunits on it)CRM Synch. Job Status Part

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 Synch. Job Status Cue
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 Code[10] —
2 Failed Synch. Jobs Δ BC24 Δ BC28 Integer Specifies the number of failed Dynamics 365 Sales synchronization jobs in the job queue. FlowField: count(“Job Queue Entry” where(“Object ID to Run” = field(“Object ID to Run”), Status = const(Error), “Last Ready State” = field(“Date Filter”)))
6 Date Filter DateTime — FlowFilter; not editable
7 Reset Date DateTime —
8 Object ID to Run Integer — FlowFilter

Keys

  • Key1: Code (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 Synch. Job Status Cue"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources