Route-Based Filtering with URLSegments Not Working in Budibase 3.8 (Table Data Not Displaying)

[asadcs]

Hi Budibase Experts,

I’m nhew to Budibase and building a dashboard app using Budibase 3.8 and running into a major issue with dynamic routing and filtering.

---

What I'm Trying to Do

• I have a dashboard showing a count of patents per year.
• When a user clicks on a year, I want to navigate to a screen like /patentdetails/2023 and display:
  • A table filtered to show only the records for that year.
  • A heading text like Selected Year: 2023 using {{ URLSegments.1 }}.

---

What’s Not Working

• The navigation to /patentdetails/2023 does occur, but the data table is empty.
• The dynamic binding {{ URLSegments.1 }} does not render in a text block — nothing is shown.
• I’ve published the app and tested it in the live environment (not the preview mode), but the issue persists.

---

What I’ve Tried

1. Set the route for the screen to /patentdetails/:year.
2. Configured the DataProvider to filter:

   Field: Year
   Operator: Equals
   Value: {{ URLSegments.1 }}
   

3. Verified that the data exists for years like 2023 and 2024.
4. Confirmed that filtering with a hardcoded year value (e.g., 2023) displays data correctly.
5. Changed the Year field from Text to Number and tested both types.
6. Used the "Navigate to" action on table row click:

   /patentdetails/{{ row.Year }}
   

7. Confirmed the URL updates correctly to /patentdetails/2023, and the screen does not redirect to the default /dashboard.

Additional Observations

• The text block using {{ URLSegments.1 }} shows nothing, indicating that the value isn’t accessible.
• When switching back to a static value or hardcoded filter, everything works — so the data source and table setup are correct.

---

What I Need Help With

• Is {{ URLSegments.1 }} still the correct way to access dynamic values from the URL in Budibase 3.8?
• Are there any known limitations with dynamic screen routing and binding?
• Could this be a bug, or is there an additional step required to make dynamic segments bind correctly to DataProviders and components?

I’ve gone through several threads and followed multiple suggestions from the community and ChatGPT, but haven’t been able to get this to work. Any help or working example would be greatly appreciated.

Thanks,
Muhammad

[mikesealey]

Hey @asadcs

You seem to be trying to navigate to page that doesn't exist.
You're navigating this page:

But I can see your screens list here doesn't contain that:

Lets go back to the start - I've got an example here that I'll work with, but you can apply these principals to your app.

I've got the Budibase sample table "Inventory" displayed in a table here. I also added a button "Navigate to Row"

Notice that I also have a screen /item/:item_ID

I've passed the Item ID into the URL of the navigate-to action, in place of :item_ID

Next, when I head to my screen /item/:item_ID I can see in the "General" settings an additional option - Set temporary URL variables for design preview

I know that Item IDs are just numbers 1-10, so I can pop a 1 in here. I can then see this reflected in the Bindings list on the left

On my screen, I've also got a table showing the Inventory table, but I'll add a filter to it.

Clicking the ⚡ Lightning bolt here will allow me to specify one of the Bindings.
Bindings >> URL >> item_id now shows as that 1 that I applied earlier

And reflected in my table is a single row, with an item_id of 1

Please remember to check the documenation for this sort of thing - paths such as this are frequently covered there.
https://docs.budibase.com/docs/url-parameters