<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic eSearch widget with WAB 1.2 - unexpected results in Attribute table in Web AppBuilder Custom Widgets Questions</title>
    <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849622#M10747</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&amp;nbsp; Has anyone else seen this behavior?&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some details:&lt;/P&gt;&lt;P&gt;&amp;nbsp; I have the "show in attribute table Widget" box checked in the config for the search layer.&amp;nbsp; The eSearch widget does the query correctly, displays the results in the widget correctly, then sends a "layer" object to the attribute table.&amp;nbsp; The debugger shows the definition query on the layer object to be intact.&amp;nbsp; The network traffic then shows the attribute table logic kicking off 2 queries.&amp;nbsp; The first is a "return county only" query, has the correct where clause, and has a response with the correct count of features.&amp;nbsp; 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.&amp;nbsp; 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".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Aug 2015 18:58:51 GMT</pubDate>
    <dc:creator>SebastianRoberts</dc:creator>
    <dc:date>2015-08-13T18:58:51Z</dc:date>
    <item>
      <title>eSearch widget with WAB 1.2 - unexpected results in Attribute table</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849622#M10747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&amp;nbsp; Has anyone else seen this behavior?&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some details:&lt;/P&gt;&lt;P&gt;&amp;nbsp; I have the "show in attribute table Widget" box checked in the config for the search layer.&amp;nbsp; The eSearch widget does the query correctly, displays the results in the widget correctly, then sends a "layer" object to the attribute table.&amp;nbsp; The debugger shows the definition query on the layer object to be intact.&amp;nbsp; The network traffic then shows the attribute table logic kicking off 2 queries.&amp;nbsp; The first is a "return county only" query, has the correct where clause, and has a response with the correct count of features.&amp;nbsp; 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.&amp;nbsp; 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".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Aug 2015 18:58:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849622#M10747</guid>
      <dc:creator>SebastianRoberts</dc:creator>
      <dc:date>2015-08-13T18:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: eSearch widget with WAB 1.2 - unexpected results in Attribute table</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849623#M10748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sebastian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; It seems there is some work I have to do to the eSearch for WAB 1.2 When I release a 1.2 version of the eSearch it should have this fixed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Aug 2015 19:04:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849623#M10748</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2015-08-13T19:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: eSearch widget with WAB 1.2 - unexpected results in Attribute table</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849624#M10749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sebastian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I did not test this when I responded to you I just assumed it was something I need to work on for 1.2. But how that I am actively in the eSearch 1.2 update process I am NOT see this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you give me any more info so that Can try and duplicate this? Do you have a definition query applied to the layer before you search? Is is all your layers that act this way?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2015 02:47:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849624#M10749</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2015-08-14T02:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: eSearch widget with WAB 1.2 - unexpected results in Attribute table</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849625#M10750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Thanks for following up.&amp;nbsp; I'm using your eSearch 1.1.11.&amp;nbsp; Attached is my config file for the widget. Would that help?&amp;nbsp; It uses just one public map service for the search, so you could just drop it in to an app.&amp;nbsp; It does not have a definition query.&amp;nbsp; Below is a screenshot of a result.&amp;nbsp; You see that your widget has the correct results, but the attribute table lists 1500 records (max allowed by the service), though it claims to be showing only 1 feature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="2015-08-14_083818.png" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/122384_2015-08-14_083818.png" style="width: 706px; height: 437px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2015 15:43:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/esearch-widget-with-wab-1-2-unexpected-results-in/m-p/849625#M10750</guid>
      <dc:creator>SebastianRoberts</dc:creator>
      <dc:date>2015-08-14T15:43:53Z</dc:date>
    </item>
  </channel>
</rss>

