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; } } }

Search: "Pagination is not supported."

BenFousek

Trying to get the new Search running against a feature layer. enableSuggestions and enableSuggestionsMenu are false. Don't see anything else in docs which warns of 10.3/supportsPagination = true.

Any help appreciated.

sources: [{
  featureLayer: new FeatureLayer('.../Parcels/FeatureServer/0', {
  outFields: ['*']
  }),
  searchFields: ['ADDRESS', 'PARCEL_ID', 'OWNER'],
  displayField: 'ADDRESS',
  exactMatch: false,
  outFields: ['*'],
  name: 'Parcels',
  placeholder: 'Search parcels',
  enableSuggestions: false,
  enableSuggestionsMenu: false,
  minCharacters: 3
}]

Find more posts tagged with

Accepted answers

khutchins

There is currently a bug with the search widget that requires services to support pagination. This bug will be fixed for the next release. You can workaround it in your application by setting maxResults to a string if the layer doesn't support pagination. Here's some code that shows how that might work.

                //workaround to handle bug with pagination remove at 3.14
                array.forEach(defaultSources, lang.hitch(this, function (s) {
                    var paging = this._supportsPagination(s);
                    if (!paging) {
                        s.maxResults = "foo";
                    }
                }));



        _supportsPagination: function (source) {
            // check if featurelayer supports pagination remove at 3.14
            var supported;
            if (source.locator) {
                supported = true;
            } else if (source.featureLayer) {
                // supports pagination
                if (source.featureLayer.advancedQueryCapabilities && source.featureLayer.advancedQueryCapabilities.supportsPagination) {
                    supported = true;
                }
            }
            return supported;
      }

All comments

NikhilSharma

Hi Guys,

Just to inform all that I got rid of this error for a feature layer from a map service(mapserver/0) simply by checking if pagination is supported or not for all the sources inside a for loop. Here is the code snippet:

search.on("load", function () {

var sources = search.sources;

sources.push({

featureLayer: layer,

enableLabel: false,

searchFields: ["STATE_NAME"],

displayField: "STATE_NAME",

exactMatch: false,

outFields: ["*"],

infoTemplate: new InfoTemplate("Ecological Footprint", "<a href= ${URL} target=_blank ;'>Additional Info</a>OBJECTID : ${OBJECTID }")

});

for(i=0;i<sources.length;i++)

{

var supported;

if (sources.featureLayer) {

// supports pagination

if (sources.featureLayer.advancedQueryCapabilities && sources.featureLayer.advancedQueryCapabilities.supportsPagination) {

supported = true;

}

if (!supported) {

sources.maxResults = "food";

}

search.set("sources", sources);

});

search.startup();

I am attaching a working sample application along with this as well.

Hope that helps.....

Regards,

Nikhil. !

SearchPagination.html.zip

NikhilSharma

Hi Guys,

search.on("load", function () {

var sources = search.sources;

sources.push({

featureLayer: layer,

enableLabel: false,

searchFields: ["STATE_NAME"],

displayField: "STATE_NAME",

exactMatch: false,

outFields: ["*"],

infoTemplate: new InfoTemplate("Ecological Footprint", "<a href= ${URL} target=_blank ;'>Additional Info</a>OBJECTID : ${OBJECTID }")

});

for(i=0;i<sources.length;i++)

{

var supported;

if (sources.featureLayer) {

// supports pagination

if (sources.featureLayer.advancedQueryCapabilities && sources.featureLayer.advancedQueryCapabilities.supportsPagination) {

supported = true;

}

if (!supported) {

sources.maxResults = "food";

}

search.set("sources", sources);

});

search.startup();

I am attaching a working sample application along with this as well.

Hope that helps.....

Regards,

Nikhil. !

SearchPagination.html.zip

khutchins

Tom Wayson correct suggest is only available if you are working with a 10.3 geocoding service that has suggest capability or a 10.3 feature layer that supports pagination.

TomWayson

Thanks Kelly, that workaround stopped the error for me.

However, it should be noted that it appears that suggestions will not be enabled for sources that do not support pagination.

khutchins

Sorry Ben I don't have specifics on a time frame. Julyish?

BenFousek

Thanks Kelly Hutchins

Time frame on next release?

khutchins

                //workaround to handle bug with pagination remove at 3.14
                array.forEach(defaultSources, lang.hitch(this, function (s) {
                    var paging = this._supportsPagination(s);
                    if (!paging) {
                        s.maxResults = "foo";
                    }
                }));



        _supportsPagination: function (source) {
            // check if featurelayer supports pagination remove at 3.14
            var supported;
            if (source.locator) {
                supported = true;
            } else if (source.featureLayer) {
                // supports pagination
                if (source.featureLayer.advancedQueryCapabilities && source.featureLayer.advancedQueryCapabilities.supportsPagination) {
                    supported = true;
                }
            }
            return supported;
      }

RichardMoussopo

I also noticed that the Search multiple sources widget only works for the featureServer type. I tried to search through featureLayer of type ...MapServer/0 and got the pagination error as below...

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.