You can hide the Field Service offering from the Problem Task list view by removing it from that list's filter conditions, gating the list with an ACL or before-query business rule, or stripping the offering field from the filter and search configuration. The assignment is the tricky part: an offering is a choice, not a task record, so hiding it means hiding the tasks stamped with that choice. "Searched by" needs to be defined before you touch anything. If you mean hidden from the list's own filter results, a filter condition change does it. If you mean invisible to every user running a list search, that's an ACL or a before-query rule. If you mean hidden from the filter picker so nobody can even select it, that's a dictionary and choice-list job.

The mixer in this article is the default Problem Task list. ServiceNow ships Problem Management with task tables that inherit from task, and Problem Tasks (problem_task) carry an offering reference field driven by the Service Portfolio. Field Service tasks and Field Service offerings are a separate plugin territory — Field Service Management installs its own tables and extends the work order family. Knowing which of those two worlds your problem record actually sits in determines whether you're hiding a choice, a reference, or a related list.

Get the scope wrong and you'll hide the Field Service offering globally, breaking the Field Service dispatcher's own problem-task workflow in a way that takes a change record to undo. The nine steps below cover the safe path first, then the failure cases, then the test that proves the offering is unfindable.

Map Which Table and Field the Problem Task List Actually Queries

Open the Problem Task list, right-click any column header, and choose Configure > List Layout. The breadcrumb at the top of the form names the exact table — usually problem_task, which extends task. That breadcrumb is your ground truth. Do not configure on the task table unless you've confirmed the list is genuinely built on the parent, because carrying a filter up to task leaks the change into every incident, change, and request list in the instance.

The offering column itself comes from a reference field typically labeled Offering that points to the Service Offering table (service_offering). In ServiceNow's data model, the offering on a task is a reference, not free text — so "Field Service offering" is a record in the service portfolio, not a string. That distinction matters: hiding a string means deleting a filter clause; hiding a record means controlling which tasks reference it.

Check the field's dictionary entry by searching sys_dictionary for the table name and offering column. Note the column's type and whether it references service_offering directly or through a dependent field on the task. Dependent reference fields (offering filtered by service) behave differently in list filters — they may not appear as a plain selectable column at all.

If your Field Service problem tasks live on a custom or FSM-installed table instead, the breadcrumb will say so, and every step below applies to that table name in place of problem_task. Verify before proceeding; the single most common mistake in this configuration is assuming the table name.

Choose Between Filter Condition, ACL, and Before-Query Rule Before You Build

Three mechanisms can hide Field Service offering records from a list, and they answer different questions. Pick by intent, not by habit.

Mechanism What it hides Who it affects Reversible without data change Best for
Default list filter condition Tasks where Offering = Field Service, from the shipped list Everyone who hasn't saved a personal filter Yes — edit the filter back Making the default view clean
Before-query business rule on problem_task Matching records before any query returns Everyone, including API and reports Yes — deactivate the rule Hard restriction on searches
ACL on problem_task.offering (read deny) The field value on matching records Users without a qualifying role Yes — disable the ACL Hiding the value but not the task
Choice-list removal / dictionary change The offering from selector pickers Everyone instance-wide Yes — but wider blast radius Preventing selection, not hiding results

The table's first column is the safe default. Filter conditions live on the list configuration record, so a bad edit is one form restore away. The business-rule path is the only one that reliably stops a filtered list search from returning matching records — it fires on query execution regardless of who authored the filter.

Choose the ACL path only if you want the task visible but the offering value masked. That satisfies "cannot be searched by" in the narrow sense that a search on the field's value returns nothing, while the task itself remains reachable. Anyone who needs the task to disappear from results should use the business rule instead.

Confirm your intended audience before committing. A rule scoped to a group (gs.hasRole() in the condition) hides the tasks from that group only, and the failure case is predictable: the Field Service dispatcher loses visibility of their own records and raises an incident against you.

Strip the Field Service Offering From the Default Problem Task List Filter

Right-click the Problem Task list header → Configure > Filter. The condition builder shows every clause the shipped list uses. Locate the clause referencing Offering = Field Service and remove it, or change the operator to is not if you want the inverse.

1: Navigate to Problem > All Problem Tasks (or the exact module your team uses). 2: Right-click a column header and select Configure > Filter. 3: In the condition builder, find the Offering clause. It typically reads [Offering] [is] [Field Service]. 4: Click the clause's remove control and confirm the remaining conditions still return the task set you expect. 5: If the inverse is what you want, set the operator to is not and leave the value as the Field Service offering record. 6: Save the filter. The list now excludes those tasks from the default view.

This changes the shared default for everyone who hasn't personalized it, so test with a non-admin account that has never customized the list. A saved personal filter on a user's account overrides the shared default entirely, and no amount of default-filter editing will defeat that. The close-out is to confirm the clause you removed wasn't the only thing keeping noise out of the list — after saving, spot-check the record count against a pre-change screenshot.

Failure handling: if the condition builder refuses to save the change because the filter is pinned by a related list or a scheduled job, the filter is being reused elsewhere. Search sys_filter for the table name to find every record referencing that filter before editing. Editing a shared filter in place can silently change what a scheduled report emails each morning.

Gate Searches With a Before-Query Business Rule on Problem Task

A before-query business rule intercepts the query before it reaches the database, which is what makes it the right tool for a "cannot be searched" requirement. The rule adds an encoded query restricting out the Field Service offering, and the list, global search, and any list-backed report all respect it.

1: Open System Definition > Business Rules and click New. 2: Set Name: Hide Field Service offering from Problem Task queries. 3: Set Table: Problem Task (confirm the exact table name from your earlier breadcrumb). 4: Set When: before query. Set Advanced: true. 5: In the Condition field, add gs.hasRole('problem_manager') only if managers must retain visibility; otherwise leave blank. 6: In the script area, add: current.addQuery('offering', '!=', '<sys_id of Field Service offering>'); 7: Set Active true and click Submit.

That script enforces the exclusion at query build time. Every consumer that respects addQuery — list views, dashboards, reports — gets the restriction without further work. Note the asymmetry: != returns records where offering is set to something other than the Field Service record, but records with an empty offering may or may not appear depending on how the choice field is populated on the record; verify with a null-offering task in the test.

The catch is scope. A before-query rule on problem_task won't fire on a query built against task. If any list query targets the parent table, add the same rule there or accept the gap. The rule also has to be scoped to the domain or conditions you care about — a global rule stops the Field Service team from finding their own problem tasks through search, which triggers a P1 ticket in the schedule's first week.

Deactivate rather than delete if you need to roll back. Post-change verification belongs in the same change record: log what you did, the exact table, the rule name, and the test results so the next admin can undo it without rediscovering the path.

Run the Filter-Out Test With a Non-Admin Account

The only test that proves the requirement is one that runs as a user without elevated roles. Admins bypass many list restrictions by role, so an admin-run test proves nothing about what a fulfiller sees.

1: Log in as a test user with the same role set as the target audience. 2: Open the Problem Task list module and record the total record count. 3: In the list search bar, type the Field Service offering name and press Enter. 4: Confirm the returned set excludes any task whose Offering reads Field Service. 5: Open the filter breadcrumb and check whether the offering clause is present or absent. 6: Repeat the search on the parent task list if your rule was scoped there. 7: Run the same search from Global Search — list rules don't always restrict global search, so this step often reveals a gap.

Step 7 is the one most teams skip, and it's where the requirement usually fails. Global search uses its own index and its own query path, so a list filter change frequently leaves global search returning the tasks. A business rule that adds a query helps list-backed results but does not necessarily suppress search-results-table hits. Confirm on the target instance, not on the belief that "it should work."

A parallel test as the Field Service dispatcher matters just as much. If you've locked the offering to everyone, the dispatcher's list goes empty, and that's a production incident. Run both tests before promoting.

Resolve the "Cannot Be Searched" Gap in Global Search and Reports

ServiceNow's global search runs against indexed search tables maintained by the search engine, not against the live problem_task query. A before-query business rule adding addQuery will block list views and list-backed reports, but global search goes through the Zing search architecture and its own query API — the rule is not guaranteed to apply there. This is the gap between "not in the list" and "cannot be searched."

The robust answer to the global-search gap is the search-source side: the Problem Task search source, its indexed table, and any search group members that include problem_task can be reviewed in Search > Search sources. A source can be excluded from the default search group, and that exclusion is the honest fix for "cannot be searched" — but it also hides problem tasks from global search entirely, including where you want them found.

Reports sit between the two. Scheduled reports built on a list filter respect the list config; reports with an encoded query written into the report definition may bypass it. Audit report definitions referencing problem_task with criteria on the offering before you promise full invisibility. A report you didn't check is the failure case that surfaces three weeks later in a compliance review.

Health and access diagnostics for search are outside this topic's scope, and this article is technical guidance, not security certification. If the requirement is regulatory rather than cosmetic, have your instance owner confirm the search-source exclusions with a qualified ServiceNow architect before relying on them.

Avoid the Instance-Wide Trap of Deleting the Offering Choice

Removing the Field Service offering from the choice list or deleting the underlying service_offering record looks like a shortcut. It is the riskiest move in this whole configuration.

The offering reference on a problem task points to a real service portfolio record. Deleting or deactivating that record orphans every task that references it, and orphaned references on a task table create validation and display failures that show up in the field service dispatcher's queue first. Choice-list changes don't govern reference fields anyway — the offering picker draws from the Service Portfolio table, so editing a choice list on problem_task may not affect the selector at all.

The correct scope-control move is to deactivate the offering in the Service Portfolio rather than delete it, and only if no active Field Service workflow depends on it. Deactivation stops new selection; it does not stop existing tasks from carrying the value, so it doesn't satisfy a hiding requirement on its own. Pair it with the filter condition from earlier if that's the combination you need.

Version differences matter here. Older ServiceNow releases populated the offering field differently from current ones, and the dependent reference behaviour (offering filtered by service) was tightened in later releases. Confirm the field's dictionary and the release notes for your instance version before assuming a deactivation hides anything. If you're unsure, the safe order is filter condition first, business rule second, portal configuration never.

Restore the Field Service Dispatcher's Own View Before You Close

Before closing the change, log back in as the Field Service dispatcher and confirm their problem list is intact. If the dispatcher's role set overlaps the restriction, the rule is too broad. The correct split: hide the offering from the general problem list, keep it visible to anyone whose job is dispatching or resolving Field Service work.

The clean version of that split in ServiceNow is a condition on the business rule rather than a table-wide rule: restrict when the user does not hold the dispatcher role, and leave the dispatcher's query untouched. Verify by running the filter-out test twice — once as the fulfiller, once as the dispatcher — and confirm the two record counts differ in the expected direction.

If the dispatcher's view is already broken because a previous admin did something similar, the restore path is to deactivate the restrictive rule, confirm the default list filter condition, and check the user's saved filter. A saved filter on a personal account hangs around after the rule change and produces confusing "it's back but only for Jane" reports.

Log both test results in the change record. The next admin will thank you.

FAQ

Does hiding the offering from the Problem Task list remove it from the Service Portfolio?

No — hiding a field value in a list never touches the Service Portfolio record. The offering remains an active service_offering record and can still be referenced elsewhere. Use deactivation in the portfolio if you want to stop new selection, and confirm on your instance's Service Portfolio module that the record is inactive before assuming the picker has changed.

The likeliest cause is that user's own saved filter or an inherited role. Saved personal filters override the shared default list configuration, and a role-elevated user may bypass the business rule entirely. Check the user's filter breadcrumb first, then confirm the rule's condition doesn't exclude their role set.

Can I hide only from a specific team instead of everyone?

Yes, if you scope the before-query business rule with a gs.hasRole() condition tied to a group. The rule fires only for users outside that role, leaving the team's view intact. Test with one member of the team and one person outside it before promoting, because a mis-scoped group condition produces an empty list for the wrong audience.

What's the risk of a before-query rule versus just changing the filter?

The rule applies to every query against the table, including APIs, dashboards, and list-backed reports, and it can't be undone from the list UI. The filter is cosmetic and reversible from the list configuration. The rule is appropriate when the requirement is "cannot be searched"; the filter when the requirement is "not shown by default." Match the tool to the wording of the requirement.

Does hiding the offering field also hide the tasks in reports scheduled by another admin?

Not reliably — scheduled reports may carry their own encoded query. Audit any report definition that references problem_task with offering criteria before declaring the tasks invisible. The verification path is to open each scheduled report's definition and check whether the encoded query includes the offering field, then run it as a non-admin to compare outputs.

Will this break the Field Service dispatcher's queue, and how much rework does that cost?

It can, and the rework is usually a rollback of the change plus a re-scoped rule. The safe order is a rule condition that exempts the dispatcher role, then testing the dispatcher's list as itself before go-live. A production incident from a locked dispatcher list typically costs more admin time to unwind than the original change did to build.

Is there a version-specific difference in how the offering field behaves?

Yes — ServiceNow releases have changed the dependent reference behaviour on offering fields over time, and older releases populated the offering reference differently from current ones. Confirm the field's dictionary entry and your instance's release notes before assuming a deactivation or a filter change behaves the same way as in a documentation example. When in doubt, test on a sub-production instance first.

This article is general technical configuration guidance for ServiceNow administrators, not a security certification or a compliance opinion; verify search-source exclusions and any regulatory requirement with your instance owner and a qualified ServiceNow architect before relying on them, and confirm the field and table names on your specific release before applying any change.