Skip to content

Shop Floor Insight · Set up

Fields Included in Shop Floor Insight’s Search Field

Last updated October 15, 2026

For production order dispatch, Shop Floor Insight searches routing lines in a fixed sequence. The first successful search stage determines the results. Later stages are skipped, and results from different stages are not combined.

This article describes standard production routing searches. Customizations can change this behavior.

Filters affect the search results.  Refer to the following related guides on configuring filters.

Searches apply within Shop Floor Setup’s configured filters and the client configuration’s existing filters.

Shop Floor Setup filters provide global restrictions across client configurations. As a best practice, configure a client configuration for each scanning station, with filters restricting the dispatch list to the work relevant to that station.

Common filtering requirements include:

  • Capacity No.
  • Work Center No.
  • Operation Routing Status.
  • Operation No.
  • Remaining quantity.

Other applicable screen, date, and employee filters also affect the eligible records. Entering a search does not remove these restrictions.

A blank search adds no search restriction.

It is a best practice to have a Shop Floor Client configuration per scanning station, and that the Shop Floor Client configuration have filters to restrict the production order routing lines appropriately, which will typically include:

  • Filtering on Work Center
  • Filtering on Machine Center
  • Filtering on the operation Routing Status (for example, excluding finished routing steps)

It is a best practice to have global filters on the Shop Floor Setup that help exclude production order routing lines that should not appear on the shop floor, these will typically be date based, or routing status based.

Effective searches require implementing these best practices.

Barcode processing takes priority

When Warehouse Insight is also installed and Barcode Rules are available, then enabled barcode rules are evaluated before the normal text search. If barcode processing successfully handles the entered value, the text-search sequence below is skipped. The intent here is that Warehouse Insight barcodes can then be ‘scanned’ into the search field to help find the correct production order, which when combined with best practice configuration on Shop Floor Client Configurations

Barcode processing can use decoded item information and production order line Description 2. A decoded Description 2 value is applied as an exact filter.

Text-search order

For ordinary text without filter symbols, the following stages run in order:

Stage Fields searched Matching method
1 Production Order No. Exact match
2 Operation No. Exact match
3 Routing line Description Contains, ignoring case
4 Production Order No. Contains, ignoring case
5 Operation No. Contains, ignoring case
6 Production Order No., Operation No., and routing line Description Exact match in any field
7 Production Order No., Operation No., and routing line Description Contains in any field, ignoring case
8 Production order line information and shortcut dimensions Literal, case-sensitive contains search

Stages 6 and 7 are additional combined-field checks. For ordinary text in Business Central, the preceding individual checks will generally have already found any matches in those fields.

Stages 1–7 stop at the first stage that finds at least one eligible routing line. That stage’s filter determines the matching records. The dispatch display can separately limit how many matching rows appear.

For example, an exact Production Order No. match at stage 1 prevents every subsequent search, including Description 2.

Stage 8: Production order information and dimensions

This stage runs only if stages 1–7 find no matches.

This stage is slower, because it requires searching flowfields on the Production Order Routing Line table.

Each eligible routing line is examined individually. The following fields are checked in order:

Order within each routing line Field
1 SFI Prod. Order Item No.
2 SFI Prod. Order Desc
3 SFI Prod. Order Desc 2
4 SFI Shortcut Dimension 1 Code
5 SFI Shortcut Dimension 2 Code

The item and description fields retrieve values from the associated production order line. SFI Prod. Order Desc 2 searches that line’s Description 2.

When any field contains the entered text, the routing line is collected as a match. Its remaining fields are skipped, and searching continues with the next routing line.

When does this stage stop?

Searching stops when any of these conditions is reached:

  • All eligible routing lines have been examined.
  • The maximum number of routing lines to examine has been reached.
  • The maximum number of matching routing lines has been collected.

Standard production dispatch calls allow 3,000 routing lines to be examined and use Dispatch Row Limit as the matching-line limit. If no positive matching-line limit is supplied, the search defaults to 200 matches.

These limits count routing lines, not distinct production orders. Several operations belonging to one order can consume several lines.

If matches are collected, only the collected routing lines are selected. Matches beyond either limit are excluded.

If no matches are collected, this stage does not apply a matching-record restriction. Otherwise eligible rows can therefore still be returned under the existing dispatch filters.

Why can a partial Description 2 search return different results?

Description 2 is often used by some implementations to contain ‘extra’ information to have available on the production order routing lines, sometimes adjusted with customizations to refer to a customer reference, or production order grouping, or even other document references such as a sales order, target batch, target lot, or any other kind of project related information that is specific to your implementation.

Suppose a production order line’s Description 2 contains REF12345.

Searching 12345 might match another production order number, operation number, or routing Description during stages 1–7. That stops the search before Description 2 is examined.

Searching REF12345 may avoid those earlier matches and reach stage 8, where the intended Description 2 value is found.

For example, if you searched with 12345, and had REF12345 in your description 2 field on the production order routing line, and RPO12345 as the production order number, then searching 12345 would first filter to RPO12345 and match there, completely skipping REF12345 from Description 2.  It’s then important to make sure that if you are searching by numbers to search with the appropriate prefix if you are leveraging ‘Description 2’ for a reference.

Description 2 does not require a complete-value match. Searching 12345 can match REF12345 when stage 8 runs and reaches the routing line before its limits are exhausted.

If a partial value exists in Description 2 but the expected operation is missing from the search results, first clear the search and confirm that the operation appears under the current dispatch filters. Verify that the value is on the associated production order line’s Description 2, then search using a literal substring with matching capitalization, without adding * or @. Description 2 is searched only when no earlier stage finds a match in Production Order No., Operation No., or routing Description. Its search is case-sensitive and can stop after examining 3,000 eligible routing lines or reaching the matching-line limit. Narrow the dispatch filters and repeat the search.

If the result remains unexpected:

  • Make sure your global filters on the Shop Floor Setup are correctly excluding production order routing lines that should not be displayed on the Shop Floor.
  • Make sure that your Shop Floor Client Configurations are correctly configured per scanning station, and have appropriate scanning station specific filters such as Work Center, Machine Center.
  • Make sure that the reference is not also used in other higher priority document references, such as production order number (for example if you have RPO12345 as the production order number, and REF12345 as your reference in description 2 then you should search by REF12345, not 12345, otherwise the search will filter to RPO12345 first.
  • If you are using Warehouse Insight, make sure to check your applicable barcode rules to see if there are barcode rules that would influence this.  For example, if you also have item 12345 and REF12345 in your description 2, and you also have a barcode rule that matches 12345, then 12345 will be used in the barcode rules if they are configured.
  • If you need to change the order of priority for searching and cannot resolve this with configuration, nor best practices, and you are not able to search with prefixes, and you are not able to add appropriate filters to limit the results then you might need  customization to enforce a specific search sequence.  Before considering a customization review the best practices and configure appropriate filters first.

Wildcards and case sensitivity

For stages 1–7, search values are passed to Business Central filters.

If the entered value contains no *, the contains-search stages automatically use @*text*: contains the text, ignoring case.

If the entered value already contains *, it is used as supplied. Surrounding wildcards and the case-insensitive @ are not added automatically.

Entered value Behavior in stages 1–7
touring Exact-match checks run first; contains checks ignore case.
as*mbly Matches values starting with as and ending with mbly.
*touring* Explicit contains filter; no automatic case-insensitive modifier.
@*touring* Explicit case-insensitive contains filter.

Stage 8 behaves differently: it searches for the original entered value as literal, case-sensitive text. Wildcards and filter expressions are not interpreted. For example, *touring* searches for actual asterisk characters in those fields.

Entering @*touring* therefore does not make stage 8 case-insensitive.

For stages 1–7, filter values are truncated to the searched field’s maximum length, including any automatically added filter characters.

Frequently asked questions

What fields are included in the search?

Production Order No., Operation No., and routing line Description are searched first.

Only if those searches find nothing does searching continue through the production order line item number, Description, Description 2, and the two shortcut dimension codes. The tables above show the complete sequence in detail.

What symbols can be used in the search field?

For stages 1–7, * is a wildcard and @ requests case-insensitive matching. For example:

  • as*mbly matches values beginning with as and ending with mbly.
  • @*touring* matches values containing touring, ignoring case.

These stages use Business Central filter syntax. Stage 8 instead treats the entire entered value literally.

Can wildcard searches ignore case?

Yes, for stages 1–7. Enter an explicit case-insensitive wildcard filter such as @*touring*.

Ordinary text without * already receives case-insensitive matching during the contains-search stages. An explicitly entered wildcard does not automatically receive @.

The stage 8 search remains case-sensitive. Changing that behavior requires customization.

Does Routing Status affect searching?

Routing Status is not a searched field and does not control the search sequence *however* it is a best practice and common for Routing Status to be included where appropriate for the process as a filter on the Shop Floor Client Configuration or the Shop Floor Setup (for example, to exclude finished routing steps).

A configured Routing Status filter can affect which routing lines are eligible. Simply having a populated status does not change the matching rules.

How many additional fields can be added to the dispatch list?

Additional fields require developer customization. The fields, their source, and any search requirements must be specified.

Displaying an additional field does not automatically make it searchable. Searching it requires separate integration with the search events described below.

Can searching be restricted to one custom field?

Yes. A developer can replace the standard search with a filter on a specific field. The following example demonstrates this approach.

Developer integration hooks

The following integration events are published by codeunit SFI AL Hooks:

Events Purpose
OnBeforeProdDispatchSearch / OnAfterProdDispatchSearch Run before and after the shared search for standard production dispatch. Expose the search text and routing record by reference.
OnBeforeProdGroupDispatchSearch / OnAfterProdGroupDispatchSearch Corresponding events for grouped production dispatch.
OnBeforeSearchDataProdOrderRouting Runs at the start of the shared search. Exposes the routing record, search text, both search limits, and a handled flag. Can replace the standard search.
OnAfterSearchDataProdOrderRouting Runs after normal text-search processing. It is skipped when processing exits earlier, including a handled before-event, blank search, or successful barcode search.

The dispatch before-events and after-events surround the shared search. The shared before-event provides the explicit handled flag for replacing its behavior.

Example: Search only “my custom field”

This example assumes a normal stored Text field named my custom field already exists on Prod. Order Routing Line.

Every nonblank search becomes a case-insensitive contains search on that field. It replaces the standard barcode and text search; it does not add the field to the standard sequence.

codeunit 50100 "Custom SFI Routing Search"
{
    [EventSubscriber(
        ObjectType::Codeunit,
        Codeunit::"SFI AL Hooks",
        'OnBeforeSearchDataProdOrderRouting',
        '',
        false,
        false)]
    local procedure OnBeforeSearchDataProdOrderRouting(
        var precProdRoutingLine: Record "Prod. Order Routing Line";
        var ptxtSearch: Text;
        var piMaxRecordsToAdd: Integer;
        var piMaxRecordsToSearch: Integer;
        var pbHandled: Boolean)
    var
        liPreviousFilterGroup: Integer;
    begin
        if pbHandled or (ptxtSearch = '') then
            exit;

        liPreviousFilterGroup := precProdRoutingLine.FilterGroup();

        // Reserve this filter group for this customization.
        // Other dispatch filters remain in their existing groups.
        precProdRoutingLine.FilterGroup(100);
        precProdRoutingLine.SetFilter(
            "my custom field", '@*%1*', ptxtSearch);
        precProdRoutingLine.FilterGroup(liPreviousFilterGroup);

        pbHandled := true;
    end;
}

Use an available codeunit ID and reserve filter group 100 for this customization.

The example uses Business Central filter syntax, so special filter characters in the entered value retain their filter meaning. It applies a filter directly rather than collecting marked records; the standard fallback’s 3,000-line scan limit does not apply. Dispatch display limits still apply.

The example changes searching only. Displaying the custom field as a dispatch column is a separate change.

When doing a customization

Here are several things to consider when doing a customization:

  • It is a new dispatch web service page that must be API compatible with the existing one including any updates to the product. The user can add data, but they cannot take things away.
  • Is the data already on the production order routing line, and if not, where is it?  The farther away from the production order line, the slower the retrieval is (e.g., trying to get customer details on a make-to-order can slow things down).
  • Does the new data need to be searched? If it does, those additional hooks described previously also need to be connected in.
  • These types of customizations in general need to be updated when the product updates.

View this article as Markdown

Still need help?

Ask other Business Central users in the Insight Works community, or send the details to the support team. Include the steps you took and any error message you saw.