# Search Application limitations
**URL:** https://community.nextw.com/t/search-application-limitations/1296
**Category:** Nextworld Platform
**Created:** [October 3, 2025, 1:48pm UTC](https://community.nextw.com/t/search-application-limitations/1296 "2025-10-03T13:48:12Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@maritha.barnard](https://community.nextw.com/u/maritha.barnard)
#### Post date: [October 3, 2025, 1:48pm UTC](https://community.nextw.com/t/search-application-limitations/1296/1 "2025-10-03T13:48:13Z")
Are there limitations to the capabilities of a search app with respect to Event Actions? In this example, I have a Mini-App, for instance YYYYYY to search Customers. I call this from XXXXXX in the Search Actions. If, in YYYYY, I put a Logic Block to do certain checks on a Form Init Event, It does not look as if it hits the Logic Block. If I put the Application in a Field action on XXXXX, it triggers the LB.
So I am asking what the difference is calling an application from a search action as opposed to a field action?
---
### Author:  [@joeyates23](https://community.nextw.com/u/joeyates23)
#### Post date: [October 3, 2025, 2:42pm UTC](https://community.nextw.com/t/search-application-limitations/1296/2 "2025-10-03T14:42:39Z")
Most search actions are going to standard list views. A standard list view does not run form init logic. So this is not something specific to a search action, that is how all standard list views work. Is they type of your search action a standard app? The only list views where you could run form init would be an advanced list applications with the advanced list form init event.