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

Page 5371 "CRM Synch. Job Status Part"

Base Application · Microsoft.Integration.Dataverse

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 5370 "CRM Synch. Job Status Cue" (relates to)CRM Synch. Job Status CueCodeunit 5371 "CRM Synch. Job Management" (calls)CRM Synch. Job Management

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 · captioned “Microsoft Dynamics 365 Sales Synch. Job Status” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Microsoft Dynamics 365 Sales Synch. Job Status
SourceTable CRM Synch. Job Status Cue
PageType CardPart

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Control1 Failed Synch. Jobs Failed Synch. Jobs Specifies the number of failed Dynamics 365 Sales synchronization jobs in the job queue. from the table field

Actions

Group Action ToolTip Runs
Processing Edit Job Queue Entries Change the settings for the job queue entry. Page 672 “Job Queue Entries”
Microsoft Dynamics 365 Connection Setup Specifies information related to the Dynamics 365 Sales connection. Page 5330 “CRM Connection Setup”
Reset Reset the synchronization status.

Triggers

OnOpenPage

Relations

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.

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: "page", object_name: "CRM Synch. Job Status Part"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources