BC Observatoryunofficial, made by waldo
tableextensionIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table extension 6618 "FS Integration Record"

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService

Open in Claude6618.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Table 5331 "CRM Integration Record" (relates to)CRM Integration Record

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 CRM Integration Record.

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 Archived Service Order Boolean — DataClassification SystemMetadata
12001 Archived Service Order Updated Boolean — DataClassification SystemMetadata
12002 Archived Service Header Id Guid — DataClassification SystemMetadata
12003 Archived Service Line Id Guid — DataClassification SystemMetadata
12004 Skip Reimport Boolean — DataClassification SystemMetadata

Keys

  • Key1: Archived Service Header Id
  • Key2: Archived Service Line Id

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 Integration Record"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources