Page 5925 "Fault Areas"
Base Application · Microsoft.Service.Maintenance
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Service.Maintenance · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Fault Areas |
| SourceTable | Fault Area |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | Service |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Code | Code | Specifies a code for the fault area. from the table field |
| Description | Description | Specifies a description of the fault area. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Import IRIS to Area/Symptom Code | Import the International Repair Coding System to define area and symptom codes for service items. | XMLport 5900 “Imp. IRIS to Area/Symptom Code” |
Relations
- source table Table 5915 “Fault Area”
Pages and codeunits on this table
- Table 5915 “Fault Area” (lookup page)
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: "page", object_name: "Fault Areas"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.