AnsweredAssumed Answered

eSearch widget with WAB 1.2 - unexpected results in Attribute table

Question asked by SRoberts on Aug 13, 2015
Latest reply on Aug 14, 2015 by SRoberts

I'm using the eSearch Widget, and noticed that when I migrated my app to WAB 1.2 that I get the map service max records returned to the Attribute table.  Has anyone else seen this behavior?  I'm not sure if this is even an issue with the eSearch widget or the attribute table, but I don't see the same thing happening with the query widget or the Esri supplied Search widget, so I thought I would try posting here first to see if anyone else has noticed the same behavior.

 

Some details:

  I have the "show in attribute table Widget" box checked in the config for the search layer.  The eSearch widget does the query correctly, displays the results in the widget correctly, then sends a "layer" object to the attribute table.  The debugger shows the definition query on the layer object to be intact.  The network traffic then shows the attribute table logic kicking off 2 queries.  The first is a "return county only" query, has the correct where clause, and has a response with the correct count of features.  The second query has a where clause of "1=1", so returns the max number of features allowed by the map service and lists those in the attribute table.  So in my case, when my search should return 15 features, the Attribute table contains 1500 features, but at the bottom says "15 features 0 selected".

Outcomes