tableextensionService Managementofficial - Microsoftderived - from the source, no model text

Table extension 6456 "Serv. Resource"

Base Application · Microsoft.Service.BaseApp

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 4 connected objects and pages

Table 156 "Resource" (relates to)ResourceTable 5950 "Service Order Allocation" (relates to)Service Order AllocationTable 5957 "Service Zone" (relates to)Service ZoneTable 5958 "Resource Service Zone" (relates to)Resource Service Zone

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.

Base Application · Microsoft.Service.BaseApp · BC25-30 · source at ea08af5e · facts from BC29

Extends Resource.

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
5900 Qty. on Service Order Δ BC28 Decimal — FlowField: sum(“Service Order Allocation”.“Allocated Hours” where(Posted = const(false), “Resource No.” = field(“No.”), “Allocation Date” = field(“Date Filter”), Status = const(Active))); not editable
5901 Service Zone Filter Code[10] — TableRelation Table 5957 “Service Zone” (Service Zone); DataClassification CustomerContent
5902 In Customer Zone Boolean Specifies that the resource (for example, a technician) is assigned to the same service zone as a specified customer. via Page 9229 “Res. Avail. (Service) Matrix” FlowField: exist(“Resource Service Zone” where(“Resource No.” = field(“No.”), “Service Zone Code” = field(“Service Zone Filter”))); not editable

Relations

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

Evidence 1 sources