topic Re: Query Widget Result Item Contents in ArcGIS Web AppBuilder Questions

Query Widget Result Item Contents

TonyGroeneveld — Wed, 25 Mar 2015 17:53:58 GMT

For the Query widget you can define which fields, alias, special type and order of the results. I have had no luck making these changes work or stick.

For example if you change the alias, special type or order of the result item contents and click ok. None of the changes are saved.

Re: Query Widget Result Item Contents

LeaDyrholm_Hansen — Mon, 30 Mar 2015 13:35:32 GMT

I have the exact same question!

Re: Query Widget Result Item Contents

RobertScheitlin__GISP — Mon, 30 Mar 2015 13:51:23 GMT

Tony and Lea,

I can confirm that this is a bug and you need to call esri tech support and report this so that it can be fixed. Until that time you can manually update the config_Query.json file for your app and it will work fine, it just seems like the UI is not saving the changes to the json file.

Re: Query Widget Result Item Contents

LeaDyrholm_Hansen — Mon, 30 Mar 2015 14:00:04 GMT

Thanks Robert, I have reported the bug to our Support Center here in Denmark and they will pass it on to Esri.

Re: Query Widget Result Item Contents

TonyGroeneveld — Mon, 30 Mar 2015 15:55:03 GMT

I assume the manually update of the json file only applies if you are hosting the web application yourself. I'm running it in AGOL.

Re: Query Widget Result Item Contents

MaryAnnSteinmetz — Wed, 08 Apr 2015 16:28:08 GMT

I have the same issue. I have a field that is a link, so I assume if I change the special type to link in the results setting it would return as a link in the query results. Nope, it just comes up as a text string. And, when I go back in to check the setting it's not saved. ??

Re: Query Widget Result Item Contents

RobertScheitlin__GISP — Wed, 08 Apr 2015 16:32:15 GMT

MaryAnn,

Yep this is due to a bug in the widgets settings dialog. You will have to make a manual change in the json file if you are using WAB Developer version.

Re: Query Widget Result Item Contents

MaryAnnSteinmetz — Wed, 08 Apr 2015 16:37:33 GMT

I’m using the AGOL version. Does this mean I would have to download the app and configure it myself manually? I may use another template if so.

Re: Query Widget Result Item Contents

TonyGroeneveld — Wed, 08 Apr 2015 16:46:39 GMT

If you are comfortable with editing json files, you can edit the AGOL json file using the ArcGIS Online Assistant (ArcGIS Online Assistant ).

Select I want to... View an item's json

Then pick your Web Application.

Scroll down to the Data section and click on the pencil and make your changes.

Re: Query Widget Result Item Contents

NicholasBarger — Wed, 08 Apr 2015 17:05:22 GMT

Here is some code that you might find helpful. Robert Scheitlin helped me with this section. Alows me to sort the Query Results by a specific field. I nested the If statements to capture all of the different queries. This selects them based on the ID of the service. Add the bold section of code to the existing section for _queryByObjectIds

_queryByObjectIds: function(objectIds, returnGeometry){

var queryParams = new EsriQuery();

queryParams.returnGeometry = !!returnGeometry;

queryParams.outSpatialReference = this.map.spatialReference;

queryParams.outFields = this._getOutputFields();

queryParams.objectIds = objectIds;

var layerId = this._getLayerIndexByLayerUrl(this.currentAttrs.config.url);

if (layerId === 18){

queryParams.orderByFields = ["NAME"];

}

var queryTask = new QueryTask(this.currentAttrs.config.url);

return queryTask.execute(queryParams);

Re: Query Widget Result Item Contents

MaryAnnSteinmetz — Wed, 08 Apr 2015 18:24:57 GMT

Nicholas,

Thank you but Robert pointed me to the ArcGIS Online Assistant where I was able to edit the JSON and save the change there.

It’s working now.

MaryAnn

Re: Query Widget Result Item Contents

MaryAnnSteinmetz — Wed, 08 Apr 2015 20:36:21 GMT

Thank you! That did it.

Re: Query Widget Result Item Contents

LeaDyrholm_Hansen — Fri, 10 Apr 2015 07:24:32 GMT

By the way these three bugs are now registered at Esri Support - so hopefully they'll soon be fixed 🙂

BUG-000086536 : Query Widget in the ArcGIS Online Web AppBuilder does not respect changes made to the Alias when configuring the Results Setting in the query

BUG-000085190: The contents of the Results Ordering tab in the query widget editor window resets to the default order, after closing and reopening the query editor in Web AppBuilder.

BUG-000085839: Query Widget in the ArcGIS Online Web AppBuilder does not maintain Special Type when configuring the Results Setting in the query.

Re: Query Widget Result Item Contents

StanMcShinsky — Tue, 14 Apr 2015 21:51:36 GMT

Lea Dyrholm Hansen

Thanks for sharing the BUG #s. It is nice to see this active response from ESRI to help out instead of feeling like our questions and comments get lost in the wind.

-Stan

Re: Query Widget Result Item Contents

KevinHatch — Wed, 15 Apr 2015 04:10:45 GMT

I am experiencing a strange error. On one map I run a query but I receive a Query Failed error if the results exceed a couple of hundred results . But on a second map (using the same instance of WAB Developer) I can run exactly the same query without receiving the error.

Is there a map setting I am missing that defines the total number of results?

Re: Query Widget Result Item Contents

RobertScheitlin__GISP — Wed, 15 Apr 2015 11:56:08 GMT

Kevin,

can check the json file for both of your query widgets and verify that they are configured identically?

Re: Query Widget Result Item Contents

KevinHatch — Wed, 15 Apr 2015 16:44:36 GMT

I thought that initially. But I duplicated the template, switched the web map, and rebuilt the queries and the same issue has occurred. I even used AGOL and the issue occurs there.

It is very weird:

1) If I add the web map layer directly from Map A it works just fine (query over 8000 records and they all appear) (TRUE FOR MAP A ONLY)

2) If I add the same layer above using a service URL it limits the results to ~250 records (TRUE FOR ALL MAPS)

3) If I add the exact same layer but using a different web map it limits the record size to ~250 records (TRUE FOR MAP B ONLY)

4) If I add a public layer from ARC GIS Online it works fine (TRUE FOR ALL MAPS)

The above is true for ALL tested layers. It isn't isolated to a single layer.

I have compared the layer info from the two web maps. They appear to be identical.

1) Linking to a service URL (rather then adding directly via map) on our server causes the results to be limited to ~250

2) The results off all layers in Web Map B are limited to ~250.

Re: Query Widget Result Item Contents

RobertScheitlin__GISP — Wed, 15 Apr 2015 17:01:50 GMT

Kevin,

Sounds like you need to contact tech support with your example use case, so they can confirm a bug in the widget or not.

Re: Query Widget Result Item Contents

KevinHatch — Wed, 15 Apr 2015 17:37:12 GMT

will do. Thanks.

Re: Query Widget Result Item Contents

NicholasBarger — Wed, 15 Apr 2015 18:13:09 GMT

I made some modifications to this widget around line 900. See the code below. It sorts the fields based on the layer id. You may be able to add alias / order information to this to get the information on the screen corrected.

_queryByObjectIds: function(objectIds, returnGeometry){

var queryParams = new EsriQuery();

queryParams.returnGeometry = !!returnGeometry;

queryParams.outSpatialReference = this.map.spatialReference;

queryParams.outFields = this._getOutputFields();

queryParams.objectIds = objectIds;

var layerId = this._getLayerIndexByLayerUrl(this.currentAttrs.config.url);

if (layerId === 15){

queryParams.orderByFields = ["STATION"];

}

else

if (layerId === 16){

queryParams.orderByFields = ["DEPARTMENT"];

}

else

if (layerId === 17){

queryParams.orderByFields = ["STATION"];

}

else

if (layerId === 18){

queryParams.orderByFields = ["NAME"];

}

else

if (layerId === 36){

queryParams.orderByFields = ["SITE_NAME"];

}

else

if (layerId === 31){

queryParams.orderByFields = ["NAME01"];

}

else

if (layerId === 32){

queryParams.orderByFields = ["PARK_NAME"];

}

else

if (layerId === 33){

queryParams.orderByFields = ["Name"];

}

else

if (layerId === 29){

queryParams.orderByFields = ["Name"];

}

else

if (layerId === 30){

queryParams.orderByFields = ["AGENCY_CD"];

}

else

if (layerId === 38){

queryParams.orderByFields = ["NAME01"];

}

else

if (layerId === 39){

queryParams.orderByFields = ["NAME"];

}

else

if (layerId === 10){

queryParams.orderByFields = ["Name"];

}

else

if (layerId === 11){

queryParams.orderByFields = ["NAME"];

}

else

if (layerId === 13){

queryParams.orderByFields = ["Cemetery"];

}

else

if (layerId === 12){

queryParams.orderByFields = ["Precinct"];

}

var queryTask = new QueryTask(this.currentAttrs.config.url);

return queryTask.execute(queryParams);

Hope it helps.