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

Table 6625 "FS Incident Type"

FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService

Across versions

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

Neighbourhood 2 connected objects and pages

Table 5340 "CRM Systemuser" (relates to, 2 links)CRM SystemuserTable 6618 "FS Work Order Incident" (referenced by)FS Work Order Incident

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

Properties

Property Value
TableType CRM
DataClassification SystemMetadata

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 IncidentTypeId GUID Incident Type Id caption
2 CreatedOn Datetime Created On caption
3 CreatedBy GUID Created By caption TableRelation Table 5340 “CRM Systemuser” (“CRM Systemuser”.SystemUserId)
4 ModifiedOn Datetime Modified On caption
5 ModifiedBy GUID Modified By caption TableRelation Table 5340 “CRM Systemuser” (“CRM Systemuser”.SystemUserId)
10 Name Text[100] —

Keys

  • PK: IncidentTypeId (clustered)
  • Name: Name

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

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

Evidence 1 sources