---
id: object/page/6000
type: object
title: Page 6000 "Dispatch Board"
summary: Page 6000 "Dispatch Board" in Base Application (Microsoft.Service.Document). 12 public procedures. Present since at least BC23, still in BC30.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: null
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: f8fdeb89567fe1d5643810e25f2effbd89675ea8ccf12a2036e372e67a9a93ba
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Service/Document/DispatchBoard.Page.al
    title: src/Layers/W1/BaseApp/Service/Document/DispatchBoard.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 6000
name: Dispatch Board
namespace: Microsoft.Service.Document
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 22
  events: 0
  subscribers: 0
  controls: 26
  actions: 5
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 0
  implements: 0
---

# Page 6000 "Dispatch Board"

> Page 6000 "Dispatch Board" in Base Application (Microsoft.Service.Document). 12 public procedures. Present since at least BC23, still in BC30.

Base Application · Microsoft.Service.Document · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Service/Document/DispatchBoard.Page.al) · facts from BC29

## Properties

| Property | Value |
|---|---|
| Caption | Dispatch Board |
| SourceTable | Service Header |
| PageType | Worksheet |
| UsageCategory | Tasks |
| 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 |
|---|---|---|---|
| General | Resource Filter | `ResourceFilter` | Specifies the filter that displays an overview of documents with service item lines that a certain resource is allocated to. |
|  | Resource Group Filter | `ResourceGroupFilter` | Specifies the filter that displays an overview of documents with service item lines that a certain resource group is allocated to. |
|  | Response Date Filter | `RespDateFilter` | Specifies the filter that displays an overview of documents with the specified value in the Response Date field. |
|  | Allocation Filter | `AllocationFilter` | Specifies the filter that displays the overview of documents from their allocation analysis point of view. |
|  | Document Filter | `DocFilter` | Specifies the filter that displays the overview of the documents of the specified type. |
|  | No. Filter | `ServOrderFilter` | Specifies the filter that is used to see the specified document. |
|  | Status Filter | `StatusFilter` | Specifies the filter that displays an overview of documents with a certain value in the Status field. |
|  | Customer Filter | `CustomFilter` | Specifies the filter that displays an overview of documents with a certain value in the Customer No. field. |
|  | Contract Filter | `ContractFilter` | Specifies all billable prices for the project task. |
|  | Zone Filter | `ZoneFilter` | Specifies the filter that displays an overview of documents with a certain value in the Service Zone Code field. |
| Control1 | Response Date | [Response Date](../table/5900.md#fields) | Specifies the estimated date when work on the order should start, that is, when the service order status changes from Pending, to In Process. <small>from the table field</small> |
|  | Response Time | [Response Time](../table/5900.md#fields) | Specifies the estimated time when work on the order starts, that is, when the service order status changes from Pending, to In Process. <small>from the table field</small> |
|  | Priority | [Priority](../table/5900.md#fields) | Specifies the priority of the service order. <small>from the table field</small> |
|  | Document Type | [Document Type](../table/5900.md#fields) | Specifies the type of the service document on the line. <small>from the table field</small> |
|  | No. | [No.](../table/5900.md#fields) | Specifies the number of the involved entry or record, according to the specified number series. <small>from the table field</small> |
|  | Description | [Description](../table/5900.md#fields) | Specifies a short description of the service document, such as Order 2001. <small>from the table field</small> |
|  | Status | [Status](../table/5900.md#fields) | Specifies the service order status, which reflects the repair or maintenance status of all service items on the service order. <small>from the table field</small> |
|  | Customer No. | [Customer No.](../table/5900.md#fields) | Specifies the number of the customer who owns the items in the service document. <small>from the table field</small> |
|  | Name | [Name](../table/5900.md#fields) | Specifies the name of the customer to whom the items on the document will be shipped. <small>from the table field</small> |
|  | Contract No. | [Contract No.](../table/5900.md#fields) | Specifies the number of the contract associated with the order. <small>from the table field</small> |
|  | Service Zone Code | [Service Zone Code](../table/5900.md#fields) | Specifies the service zone code of the customer's ship-to address in the service order. <small>from the table field</small> |
|  | No. of Allocations | [No. of Allocations](../table/5900.md#fields) | Specifies the number of resource allocations to service items in this order. <small>from the table field</small> |
|  | Order Date | [Order Date](../table/5900.md#fields) | Specifies the date when the related order was created. |
|  | Order Time | [Order Time](../table/5900.md#fields) | Specifies the time when the service order was created. <small>from the table field</small> |
|  | Reallocation Needed | [Reallocation Needed](../table/5900.md#fields) | Specifies that you must reallocate resources to at least one service item in this service order. <small>from the table field</small> |
| Control94 | Service Order Description | [Description](../table/5900.md#fields) | Specifies a short description of the service document, such as Order 2001. |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Dispatch Board | Show Document | Open the document that the information on the line comes from. |  |
| Planning | Resource Allocations | View or allocate resources, such as technicians or resource groups to service items. The allocation can be made by resource number or resource group number, allocation date and allocated hours. You can also reallocate and cancel allocations. You can only have one active allocation per service item. | [Page 6005 "Resource Allocations"](../page/6005.md) |
|  | Demand Overview | Get an overview of demand for your items when planning sales, production, projects, or service management and when they will be available. |  |
| Print | Print Dispatch Board | Print the information on the dispatch board. |  |
|  | Print Service Order | Print the selected service order. |  |

## Procedures

- `SetAllFilters()`
- `SetDocFilter()`
- `SetDocFilter(var ServHeader: Record "Service Header")`
- `SetStatusFilter()`
- `SetRespDateFilter()`
- `SetServOrderFilter()`
- `SetCustFilter()`
- `SetZoneFilter()`
- `SetContractFilter()`
- `SetResourceFilter()`
- `SetResourceGroupFilter()`
- `SetAllocFilter()`

Plus 10 local procedures.

## Triggers

OnOpenPage

## Relations

- source table [Table 5900 "Service Header"](../table/5900.md)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: none

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## 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: "Dispatch Board")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.