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

Table extension 6614 "FS Location"

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService

Open in Claude6614.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 14 "Location" (relates to)LocationTable 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 Location.

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 to FS Boolean Specifies if the project task is coupled to an entity in Field Service. via Page extension 6623 “FS Location List” FlowField: exist(“CRM Integration Record” where(“Integration ID” = field(SystemId), “Table ID” = const(Database::Location))); not editable

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

Evidence 1 sources