> This page is for Glide Classic.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://www.glideapps.com/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://www.glideapps.com/docs/_mcp/server.

# Screen Values

> Values that you can access from the current screen.

Occasionally you will see the option to work with **Screen values** in Glide. Screen values are useful when working with Forms or Inline Lists. Let's look at two examples.

## In Forms

Take a look at using Screen Values to filter a [Choice component](/docs/essentials/components/choice) using the inventory template.

![Screen Value Example 1](/docs/_fern-img/bb41e2125eb2d6654b415db1fac1f257660c8549d3eed43916ab0bcb43127b6d.webp)

This screen shows a user adding a new inspection. This is a [**Form**](/docs/essentials/components/form-container) screen.

In this app, there are many properties and each property has multiple units. When you pick a property, you only want to have to choose from a list of units within that property. You don't want to pick from a list of all units from all properties.

You can therefore add a [Filter](/docs/reference/user-experience/filter) on the **Choice component** that says: "Only show units where the property ID matches the property ID selected in the current screen."

## Filtering Collections

Another use case for using **Screen Values** is when you have collections.

When you have a collection, you have two contexts:

1. The row of the current screen
2. The rows of the collection

Without screen values, the collection doesn't know what screen it is being shown on. With screen values, you can use the containing screen's values in your conditions.

For example, showing a list of related items without showing the current item.

![Field Sales Screen Values Example](/docs/_fern-img/c73aa5cff151498ef98aeef4a3b202f65eda12bd6015d2f296837890a1855d4c.webp)