---
title: "Querying on Vanity URLs"
slug: "querying-on-vanity-urls"
status: "new"
updated: 2026-07-21T20:24:35Z
published: 2026-07-21T20:24:35Z
canonical: "knowledge.technolutions.net/querying-on-vanity-urls"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Querying on Vanity URLs

Forms and events can use Slate-generated public URLs or custom vanity URLs. A vanity URL is easier to read and share, but it may also need to be audited so duplicate or outdated vanity paths can be found.

Use a Configurable Joins query on the **Form** base to identify forms and events with vanity URLs.

![Example public URL that uses a form or event GUID](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/01-zt9kcI1Gx0zHMgz4MCRb6.webp)

![Example form or event vanity URL setting](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/02-3dBefRdTbaTebNCBP5fJ4.webp)

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/querying-on-vanity-urls-y6sMhdrNtqvsFcN) in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? [Let us know](https://community.technolutions.net/get-inspired/new?post_type=gnHx7As1gZ8r6Ld)!

## Build the query

1. Create a Configurable Joins query.
2. Set **Base** to **Form**.
3. Add exports such as the form title, form URL, folder, status, or any other values needed for review.
4. Add one of the filters below to return only forms and events where a vanity URL exists.

## Option 1: Exists filter

1. Add a subquery filter.
2. Set **Aggregate** to **Exists**.
3. Add a nested subquery export and set **Output** to **Formula**.
4. Add any export or literal value to the nested subquery export. The value is required to save the export, but it is not referenced in the formula.
5. Enter the following formula:

```plaintext
f__JID_.[alias]
```

![Exists subquery filter using the form alias column](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/03-2zez6tNFA7uj0w6Ogjj9x.webp)

## Option 2: Formula filter

1. Add a subquery filter.
2. Set **Aggregate** to **Formula**.
3. Enter the following formula:

```plaintext
f__JID_.[alias] IS NOT NULL
```

![Formula filter using alias IS NOT NULL](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/04-VSMYmrxmM2NxQkjzwwLeH.webp)

## Compare the options

| Method | Pros | Cons |
| --- | --- | --- |
| Exists filter | Follows a familiar subquery pattern and can be expanded if additional subquery logic is needed. | Requires a nested subquery export even though the export value is not used directly. |
| Formula filter | Directly tests whether the vanity URL alias column has a value. | Requires entering the SQL-style condition accurately. |

## Review the results

Run the query and review the forms or events returned. Include the form title and public URL exports so users can identify the records where vanity URLs are already configured.