Table 5928 "Service Status Priority Setup"
Base Application · Microsoft.Service.Document
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC282 fields changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Service.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Service Status Priority Setup |
| DataClassification | CustomerContent |
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 | Service Order Status Δ BC28 | Enum “Service Document Status” | Specifies the service order status to which you are assigning a priority. | enum Enum 5912 “Service Document Status” |
| 2 | Priority Δ BC28 | Option | Specifies the priority level for the service order status. | OptionCaption: High,Medium High,Medium Low,Low |
Keys
- Key1: Service Order Status (clustered)
Trigger event subscribers
- OnBeforeInsertEvent: Codeunit 5999 “Service Experience Tier” BlockInsertServiceStatusPrioritySetup
Relations
- drill-down page Page 5943 “Service Order Status Setup”
- lookup page Page 5943 “Service Order Status Setup”
Pages and codeunits on this table
- Page 5943 “Service Order Status Setup” (source table)
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: "Service Status Priority Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.