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.
⭐ Get Inspired
This article was adapted from a post by Technolutions staff in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? Let us know!
Build the query
Create a Configurable Joins query.
Set Base to Form.
Add exports such as the form title, form URL, folder, status, or any other values needed for review.
Add one of the filters below to return only forms and events where a vanity URL exists.
Option 1: Exists filter
Add a subquery filter.
Set Aggregate to Exists.
Add a nested subquery export and set Output to Formula.
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.
Enter the following formula:
f__JID_.[alias]
Option 2: Formula filter
Add a subquery filter.
Set Aggregate to Formula.
Enter the following formula:
f__JID_.[alias] IS NOT NULL
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.