nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcCollector search only returning 12 results

deleted-user-aT9BCrgkP4kc

Previously ArcCollector search was returning 100s' of results (which is functionality that is needed) whereas now it is only returning a maximum of 12 values whenever we search. Is there a limit placed on the amount of searches that we can change, or is this standard now?

Find more posts tagged with

Accepted answers

All comments

MarkBockenhauer

There is no user control over the amount returned. By design the 12 results closest to the center of the display are supposed to be returned. How do you want to make use of the 100's of results that you would like to see returned?

deleted-user-aT9BCrgkP4kc

Without a multi field search limiting the return hurts groups with hundreds of thousands of assets in a feature, as there are similarities across the data. We have poles that have similar naming across our state, previously being able to have 100's of results it was easy to find the right pole (not all users are standing out in front of it so just the closet one does not work for them). Is there anyway to either make a multi field search (without having to make a new field) and/or being able to pull all the results like before?

TedChapin

Along these same lines, is there any way to modify the search result label? Currently all 12 records have the layer name and a coordinate. No way to tell them apart without clicking on them. If you're doing a "contains" type of search and multiple results, need a way to modify that label.

TedChapin

It's the popup title.

MrG

Dear Mark,

We are in a hurry with this subject. We use Collector under iOS since 2015 in a very efficient way to increase the performance of the on-the-spot checks for granting the European Union subsidies for agriculture. It is a notable and important project all over Europe.

So far, so good. Until this year when we recently shifted from Collector Classic to the brand new Collector and now we are also facing with this problem of not being able to control the number of records returned by a search. This is a huge problem for us. We understand the decrease of performance of having to deal with hundreds of records, but it is a strong and critical necessity for us. The nature of our data leads to searchs that necessarily include some hundreds of records.

Please, consider the possibility of including in the options of the app one parameter to configure the maximun number of results returned by a query with a number between 12 (your default) to for example 200 or so. Once you have the array populated with the results, the behaviour should be the same as in Collector Classic: I mean... once you press in one result, the app rezooms in the center or envelope of the feature pressed.

This is a critical national project, and we will transfer our proposal officially to you using our professional services support here in Spain, but please consider to rollout an update of the app for iOS as soon as possible.

By the way: rolling back to Collector Classic is not an option because in the last version highly detailed basemaps produce a crash of the app when zooming at the largest levels of the cache (probably because of a bug). TPKs that used to work in previous releases produce crashes with the last version of Classic, which make the use of Classic not feasible. That was one of the reasons that moved us to use the new Collector.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.