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

Table extension 6613 "FS Job Cue"

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 3 connected objects and pages

Table 5331 "CRM Integration Record" (relates to)CRM Integration RecordTable 5339 "Integration Synch. Job Errors" (relates to)Integration Synch. Job ErrorsTable 9057 "Job Cue" (relates to)Job Cue

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.

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · BC29-30 · source at ea08af5e · facts from BC29

Extends Job Cue.

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
12000 Coupled Data Sync Errors Integer Specifies the number of errors that occurred in the latest synchronization of coupled data between Business Central and Dynamics 365 Field Service. via Page extension 6616 “FS Project Manager Activities” FlowField: count(“CRM Integration Record” where(Skipped = const(true)))
12001 FS Int. Errors Integer Specifies the number of errors related to data integration with Dynamics 365 Field Service. via Page extension 6616 “FS Project Manager Activities” FlowField: count(“Integration Synch. Job Errors”)

Relations

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: "tableextension", object_name: "FS Job Cue"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources