Table extension 6617 "FS CRM Product"
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
FieldServiceIntegration · Microsoft.Integration.DynamicsFieldService · BC29-30 · source at ea08af5e · facts from BC29
Extends CRM Product.
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 | FieldServiceProductType | Option | Field Service Product Type caption | OptionCaption: Inventory,Service,Non-Inventory; DataClassification SystemMetadata |
| 12001 | ConvertToCustomerAsset | Boolean | Convert to Customer Asset caption | DataClassification SystemMetadata |
Relations
- extends Table 5348 “CRM Product”
Recent changes
- 2026-07-15 #9322 [FS Integration] SVCITEM-CUSTASSET mapping ignores “Convert to Customer Asset” flag — every Service Item synced to FS unconditionally (main, BC30, fix)
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 CRM Product"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.