Date Filter not working when creating dashboard from UI Builder

[rubesh_u]

I have created date filter using UI builder and added the target table and field but it is not working when I select apply it doesn't even selects the date. but the other dashboard which is created using non-technical editor works fine. Am I missing something?

[YashwanthV18760 · Accepted solution]

Hi @rubesh_u 

It looks like the Date Filter configuration is mostly correct, but in UI Builder filters don’t automatically work unless they’re properly connected to the components and data resources. Unlike dashboards created in the non-technical editor, UI Builder requires explicit binding.

First, check whether the component you want filtered (chart, pivot, list, etc.) is actually using the same data resource that the filter targets. Open the component properties and confirm the data source matches. If the component isn’t bound to that resource, the filter won’t affect it.

Next, verify the data resource supports filtering. Go to the Data Resources panel and open the resource. If it’s static or scripted without query binding, it won’t respond to filter inputs. The resource needs to accept conditions or encoded queries.

A very common issue is missing client state binding. UI Builder filters usually pass values through a client state parameter. You need to create a client state parameter (for example, selectedDateRange), bind the filter value to that parameter, and then bind the data resource query to the same parameter. If this step is missing, clicking Apply won’t do anything because nothing is listening for the filter value.

Also confirm that the field you selected (Created) is actually a Date/Time field in the table schema. If it’s stored as a string or custom formatted value, the filter will display but won’t apply correctly.

If “Apply to hierarchy” is enabled, try disabling it unless your table actually has hierarchical relationships. That setting can prevent filtering from applying if hierarchy logic isn’t present.

Finally, test with a very wide date range like Last 5 years to make sure records actually exist in the selected range. Sometimes the filter is working but returns no rows, which makes it look broken.

Quick test: add a temporary List component using the same table and data resource. If the list updates when applying the filter, the issue is with the original widget binding. If it doesn’t update, then the problem is in the filter or data resource wiring.

In short, the filter UI is fine — it just needs proper binding from filter → client state → data resource → component for it to work.

[YashwanthV18760 · Accepted solution]

Hi @rubesh_u 

It looks like the Date Filter configuration is mostly correct, but in UI Builder filters don’t automatically work unless they’re properly connected to the components and data resources. Unlike dashboards created in the non-technical editor, UI Builder requires explicit binding.

First, check whether the component you want filtered (chart, pivot, list, etc.) is actually using the same data resource that the filter targets. Open the component properties and confirm the data source matches. If the component isn’t bound to that resource, the filter won’t affect it.

Next, verify the data resource supports filtering. Go to the Data Resources panel and open the resource. If it’s static or scripted without query binding, it won’t respond to filter inputs. The resource needs to accept conditions or encoded queries.

A very common issue is missing client state binding. UI Builder filters usually pass values through a client state parameter. You need to create a client state parameter (for example, selectedDateRange), bind the filter value to that parameter, and then bind the data resource query to the same parameter. If this step is missing, clicking Apply won’t do anything because nothing is listening for the filter value.

Also confirm that the field you selected (Created) is actually a Date/Time field in the table schema. If it’s stored as a string or custom formatted value, the filter will display but won’t apply correctly.

If “Apply to hierarchy” is enabled, try disabling it unless your table actually has hierarchical relationships. That setting can prevent filtering from applying if hierarchy logic isn’t present.

Finally, test with a very wide date range like Last 5 years to make sure records actually exist in the selected range. Sometimes the filter is working but returns no rows, which makes it look broken.

Quick test: add a temporary List component using the same table and data resource. If the list updates when applying the filter, the issue is with the original widget binding. If it doesn’t update, then the problem is in the filter or data resource wiring.

In short, the filter UI is fine — it just needs proper binding from filter → client state → data resource → component for it to work.

[rubesh_u · Accepted solution]

Thanks @YashwanthV18760 

Based on this 

https://developer.servicenow.com/dev.do#%21/reference/next-experience/utah/shared-components/sn-comp...

Under "Connect the filter to a data visualization component"

I have created a page script and mapped it to the component and now it works.