How to filter Hardware Assets using Search Input and Lookup Data Resource in UI Builder?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi everyone,
I am customizing the Asset Management Workspace → Hardware Assets page in UI Builder.
I want to create a Find Asset search where a user enters an Asset Tag (for example, P1000807) and the page displays only the matching hardware asset.
My current setup is:
Table: Hardware (alm_hardware)
Search Input component: Find Asset
Client state: search_value
Data Resource: Look up a single record / Record lookup 1
Search condition: Asset tag → is → search_value
The search condition is working/configured correctly, but I am unsure about the event configuration.
I believe I need an event on the Find Asset Search Input to:
Capture the entered asset tag.
Update the search_value client state.
Refresh/invoke the Record lookup 1 data resource.
Display the matching asset.
What is the recommended way to configure this event flow in the current UI Builder version?
Should I use Search executed, Value changed, or another event? And how should I bind the event payload to search_value and refresh the lookup data resource?
Any guidance or example would be appreciated.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
I’d lean toward using the Search executed event rather than Value changed for this use case. Updating the client state on every keystroke could cause the record lookup to run repeatedly, while Search executed lets you trigger the lookup only after the user submits the Asset Tag.
The flow I’d expect is: Search executed → capture the submitted value → set search_value → refresh/invoke the Record Lookup data resource → bind the returned record to the asset display component.
I’d also verify the exact payload exposed by the Search Input’s Search executed event in the current UI Builder version, since the payload/property names can vary by component/version. If someone has a working configuration for alm_hardware, an event mapping example would be really helpful
