Searching by common name shouldn't have any total restrictions to make sure we can select the correct constituent. In addition, we have to have access to add fields to search result to easily find the correct constituent (Constituency Code, Age, Education, ...)
Hey Fariba, thanks for posting this idea. I wanted to jump in and comment real quick to provide some context. We have big long term plans for Search in RE NXT that will effectively accomplish everything you are suggesting here (and more!). However, there are some technology based dependencies that we need to work through before it becomes a reality. It is likely a Q2 2017 (or later) initiative. In the meantime, we recognized a need to enable users such as yourself to effectively use search the way it exists in RE NXT today. This included allowing users to view more than 8 results. We still intend for search to be used to locate a single constituent record (not as a segmentation tool) and we felt that incorporating a limit of 1,000 records was more than enough results for this purpose. By implementing the limit, we shield ourselves from a potential performance impact given the way search is implemented today. While we like allowing users to view more results, we don't want that to come at the cost of a speedy search function.
So at some point I can assure you this will be implemented, but I just wanted to give you a realistic time frame and some context as to why the limit is there today. :)