Table 5952 "Resource Location"
Base Application · Microsoft.Service.Resources
Across versions
- BC23present
- BC242 fields changed
- BC25-27unchanged
- BC284 fields changed
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Service.Resources · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Resource Location |
| 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 | Location Code Δ BC28 | Code[10] | Specifies the location code of the resource. | TableRelation Table 14 “Location” |
| 2 | Location Name Δ BC24 | Text[100] | — | FlowField: lookup(Location.Name where(Code = field(“Location Code”))); not editable |
| 3 | Resource No. Δ BC28 | Code[20] | Specifies the number of the resource in the location. | TableRelation Table 156 “Resource” |
| 4 | Resource Name Δ BC24 Δ BC28 | Text[100] | Specifies the name of the resource. | FlowField: lookup(Resource.Name where(“No.” = field(“Resource No.”))); not editable |
| 5 | Starting Date Δ BC28 | Date | Specifies the date when the resource becomes available in this location. |
Keys
- Key1: Location Code, Resource No., Starting Date (clustered)
Relations
- drill-down page Page 6015 “Resource Locations”
- lookup page Page 6015 “Resource Locations”
- Location Name: CalcFormula Table 14 “Location”
- Location Code: TableRelation Table 14 “Location”
- Resource Name: CalcFormula Table 156 “Resource”
- Resource No.: TableRelation Table 156 “Resource”
Pages and codeunits on this table
- Page 6015 “Resource Locations” (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: "Resource Location"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.