Lists and filters are the fundamental tools in ServiceNow for finding and organising data without writing a single line of code. They replace the need to manually search through thousands of records, saving time and reducing errors for every system administrator. For the CSA exam, mastering lists and filters is essential because you'll be asked to retrieve specific information, create custom views, and demonstrate how to manage data efficiently in real-world scenarios.
Jump to a section
A simple way to picture Lists and Filters
Having messy laundry piles means you cannot find your favourite shirt quickly. Instead of rummaging through a heap, you sort clothes into separate piles: whites, darks, delicates, and towels. This makes washing and folding easier. In ServiceNow, a list is like your messy pile of all records—every user, every incident, every request. When you need only the high-priority incidents assigned to you, you apply a filter. The filter is like grabbing just the "whites" pile from your laundry heap. Without filters, you scroll through hundreds of records. With filters, you see exactly what you need. Just as a laundry basket organises your clothes, a list view in ServiceNow organises your data. Using filters lets you find urgent tasks instantly, just like pulling out that favourite shirt from a sorted pile. The cause is a cluttered list of all records; the effect is wasted time hunting. The solution is a filter that narrows the list to a specific, manageable set.
A list in ServiceNow is simply a table of rows and columns that displays records from a specific table, like the User table or the Incident table. Each row is one record (one user or one incident), and each column is a field (like Name, Email, or Priority). Lists are the default way you see data in ServiceNow. But sometimes you don't want to see every record—you want only the records that meet certain conditions. That's where filters come in. A filter is a rule or set of rules that tells ServiceNow which records to show and which to hide. For example, a filter might say: show only incidents where the Priority is '1' and the State is 'New'. Filters change the list dynamically without deleting any data; they just hide records that don't match. You build filters using the Filter Conditions area above the list. Each condition has three parts: a field (e.g., Priority), an operator (e.g., 'is', 'is not', 'greater than'), and a value (e.g., '1'). You can combine multiple conditions with 'AND' or 'OR' logic. A list view is a saved configuration of a list, including which columns are shown, in what order, and which filter is applied. For example, you might create a view called 'My High Priority Incidents' that only shows incidents assigned to you with Priority 1. List views are personal or public. A personal view is visible only to you. A public view is visible to everyone with appropriate permissions. You can create a new view by clicking the view icon, selecting 'Create a new view', giving it a name, and then setting your columns and filters. The list of available views appears in a dropdown next to the current view name. The reference anchor is the table that the list is based on. Every list belongs to one table. When you apply a filter, you are filtering records from that table. The personal view is the view you see by default unless you switch to another view. You can also create a copy of an existing view and modify it. Lists and filters replace the old way of finding data—manually scanning reports or asking colleagues to run queries. They empower non-technical users to find information quickly. The exam tests your understanding of how to create, modify, and share list views, and how to build effective filters. Key terms: table (the structure holding records), record (a single entry in a table), field (a single piece of data in a record), filter condition (a rule that selects records), AND/OR operators (ways to combine conditions), and view (a saved list configuration). By mastering these, you can navigate ServiceNow like a pro and answer any CSA question on this topic with confidence.
Navigate to the target table
Open ServiceNow and use the navigation menu to find the table you want (e.g., Incidents). The list shows all records from that table. This is the starting point for applying any filter or creating a view.
Open the filter conditions
Click the filter icon (usually a funnel) above the list. An area appears where you can add conditions. This opens the door to narrowing your data. Each condition you add will reduce (or expand) the displayed records.
Add a filter condition
Choose a field from the dropdown (e.g., Priority), select an operator (e.g., is), and enter a value (e.g., 1). Then click 'Add' or press Enter. The list updates to show only matching records. This is the core action of finding specific data.
Save the view
To reuse this filter later, click the view name (next to the filter icon) and select 'Save filter as a new view'. Enter a name and choose personal or public. This captures your current list configuration, including filters and column order, for future use.
Switch between views
Click the view name dropdown again and choose another view. The list changes instantly to reflect that view's saved filters and columns. This allows you to quickly access different subsets of data without rebuilding the filter each time.
An IT professional called Jamie works as a ServiceNow administrator for a medium-sized company. Every day, Jamie receives dozens of incident tickets. Jamie's job is to ensure the right people see the right tickets quickly. Without lists and filters, Jamie would have to scroll through all 2000 open incidents to find a single high-priority outage. That is impractical, so Jamie uses filters. Here is a typical morning: Jamie logs into ServiceNow and navigates to the Incident table. The default list shows every open incident—hundreds of them. Jamie wants to see only incidents assigned to the IT Support team with Priority 1. Jamie clicks the filter icon above the list. In the filter conditions, Jamie sets: 'Assigned to is one of IT Support' and 'Priority is 1'. The list updates instantly, showing only 5 incidents. Jamie then creates a personal view called 'Critical Support Tickets' so that every morning Jamie can click that view and see the same filtered list without re-entering the conditions. Jamie also shares a public view called 'Open High Priority Incidents' for the whole IT team. This view shows Priority 1 and 2 incidents that are still open, sorted by the date they were created. Team members can quickly see what's most urgent. At the end of the week, Jamie uses another list view to generate a report of all incidents closed by the IT Support team in the last 7 days. The boss asks for a list of all incidents related to a specific software update. Jamie adds a filter condition: 'Short description contains Update 2024'. This narrows down the list immediately. Without filters, Jamie would waste hours. The real power of lists and filters is that they save time, reduce human error, and allow even non-technical staff to find exactly what they need. In the CSA exam, you will be expected to demonstrate these exact actions: creating a filter, saving a view, switching between views, and understanding the difference between personal and public views. This real-world scenario mirrors the exam's focus on practical, everyday tasks a ServiceNow admin performs.
The SNOW-CSA exam tests Lists and Filters very directly. You will see questions that ask you to identify the correct steps to create a new list view, apply a filter, or modify column order. They love to test the difference between personal and public views. A common question gives you a scenario and asks which type of view to create. The correct answer is usually 'personal view' if the user wants it only for themselves, and 'public view' if they want to share with others. Another trap: they might ask what happens when you delete a personal view. Answer: only your view is deleted; the underlying data and other views remain. They also test the filter condition syntax. Questions often give you a condition and ask you to interpret which records it will return. For example, 'Active is true AND Priority is 1' returns only incidents that are both active and high priority. 'Active is true OR Priority is 1' returns all active incidents plus any inactive incidents that happen to be Priority 1. Watch out for operator confusion: 'is' vs 'is not', 'contains' vs 'starts with'. They may ask about the order of columns: you can rearrange columns by dragging column headers. They might test sorting: clicking a column header sorts ascending, clicking again sorts descending. They also test how to access list views: the view icon (a small eye or dropdown menu) next to the current view name. They love to ask about the 'Copy view' option—what it does (creates a new view based on an existing one) and what it does not do (affect the original view). Another typical question: 'Which of the following is NOT a valid filter condition operator?' Possible options include 'is', 'is not', 'contains', 'greater than', 'between'. But 'in' is not a standard operator in a basic filter (though it exists in advanced conditions). They may also test the concept of the 'Reference anchor'—the table from which the list is built. Misconception: some beginners think changing the filter deletes data. Wrong: filters only affect what is displayed, not the records themselves. Key definitions to memorise: table, record, field, filter condition, AND/OR, personal view, public view, reference anchor, column reordering, sorting. Expect at least 2-3 questions on this topic. The exam is practical: if you can create and modify a list view in the actual ServiceNow instance during your study, you will answer these questions easily.
A filter hides records from view but never deletes them from the database.
A personal view is only visible to the user who created it.
A public view is visible to all users with the appropriate permissions.
Filter conditions use field, operator, and value to select records.
Use AND to narrow results and OR to broaden results.
Clicking a column header sorts the list by that column in ascending order.
You can create a new list view by copying an existing one.
The reference anchor is the table that the list is built from.
These come up on the exam all the time. Here's how to tell them apart.
Personal View
Visible only to the user who created it
Cannot be shared with other users
Deleted only when the owner deletes it
Public View
Visible to all users with appropriate permissions
Can be shared across teams and roles
Can be deleted by any user with 'view_admin' role
Filter (temporary)
Not saved after you leave or clear it
Only affects the current list session
Cannot be reused without re-entering conditions
View (saved)
Saved and reusable any time
Includes filters, columns, sorting, and column order
Can be personal or public
AND condition
Narrows the list (fewer records)
Requires all conditions to be true
Typical for precise filtering
OR condition
Broadens the list (more records)
Requires at least one condition to be true
Typical for inclusive filtering
Filter Conditions
Simple drop-down fields with AND/OR
Easier for beginners
Limited to basic operators
Advanced Filter Conditions
Uses a text editor for complex rules
Allows nested conditions and parentheses
Supports scripts and dynamic values
Mistake
Applying a filter deletes the records that are hidden.
Correct
Filters only hide records from the current view; the records still exist in the database.
Many beginners think of filters like deleting rows in a spreadsheet, but filtering is only a visual change.
Mistake
A personal view can be seen by everyone who has the same role.
Correct
A personal view is visible only to the user who created it, regardless of roles.
Newcomers confuse personal with role-based visibility, thinking roles automatically share views.
Mistake
If you delete a public view, the records in the list are also deleted.
Correct
Deleting a public view only removes the saved configuration; the original records remain untouched.
People equate views with data, not understanding that a view is just a set of display settings.
Mistake
Adding more filter conditions always gives fewer records.
Correct
Using OR between conditions can increase the number of records shown.
Beginners assume all conditions reduce the result set, but OR expands it by including records matching either condition.
Mistake
You cannot change the columns displayed in a list view without creating a new view.
Correct
You can temporarily change columns in any view—the view name stays the same unless you save the changes as a new view.
Users think views are locked, but they can modify the current view without saving, and the change is temporary.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Only that view is deleted from your account; the data and all other views remain unchanged. You can always recreate the view later.
No, personal views are only visible to you. To share, convert it to a public view or create a new public view with the same settings.
Clear all filter conditions by clicking the 'Clear' or 'Reset' button in the filter area, or switch to an unfiltered view like 'All'. The list will show all records again.
A filter is a set of conditions that limits displayed records. A view is a saved state that includes a filter, selected columns, sorting, and other display settings. A view can include a filter, but a filter is not a view.
You may not have the 'create_new_view' or 'view_admin' role, or your instance administrator has restricted view creation. Check with your admin for permissions.
No, a filter works only on a single table. To combine data from different tables, you would need reports or other tools like saved queries.
You've finished Lists and Filters. Continue through the SNOW-CSA study guide to build a complete picture of the exam.
Done with this chapter?