Return

Understanding URL params and paths

Use the URL to load the right record, build clean links, and handle dynamic pages.

Steps at a glance

1. Understand the page path (the part after your domain).
2. Use URL parameters to pass values like an ID.
3. Read those values to load the right data.

1) Paths vs parameters

• Path: the route to a page (for example /products).
• URL parameters: extra values in the URL (for example ?search=shoes).

2) Use parameters to load data

Common pattern:

1. User clicks a link like /product?id=123.
2. Your page reads id.
3. Your page loads the record with that ID.

3) Keep links consistent

• Use the same parameter name everywhere (for example always use id).
• If you change it, update every link to avoid broken navigation.

Common pitfalls

The page loads but shows no data

• Confirm the URL has the parameter you expect.
• Confirm the parameter value matches an existing record.

Related guides

Using table views

Use views to save filters and reuse the same dataset across your project.

Beginner6 min

How to preview as a different user

Test your app as another user to validate private pages, roles, and data visibility.

Beginner4 min