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

Query Widget Result Item Contents

TonyGroeneveld

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.

Najděte více příspěvků označených jako

Accepted answers

KevinHatch

I figured out our problem. It is probably an eye rolling rookie mistake. One of the maps was referencing the layers on our web server and one on our app server. The ones referencing the app server didn't have the query limit restriction, the the ones referencing the web server did. I was referencing our web server when adding the layer URL manually.

All comments

NicholasBarger

I'm not sure. I found it fairly annoying but simple to add this code into the Query widget.js code...

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

if (layerId === 17){

queryParams.orderByFields = ["STATION"];

}

else

if (layerId === 18){

queryParams.orderByFields = ["DEPARTMENT"];

}

Just match up the layerid with the correct field name of the service.

KirkHarstead

Nicholas,

Do you know if the orderByFields parameter can be changed using the ArcGIS Online Assistant site? I've used this to change the json file for things like setting the special type and adding links to the upper banner. But I can't seem to find any information on the orderByFields parameter in the json through the Online Assistant. I would really like to change the order of the results window after a query is run, so any help on this issue would be much appreciated! Thank you.

MalcolmEchaluce

I imported this app in the the Developer WAB from an AGO developed on with the queries already set up. Should I re-setup the queries in WAB Developer version or should it have (in theory) carried over properly for it to then show up in the config.json for the Query widget?

NicholasBarger

Malcolm,

Use the WAB to initially set up the Queries that you want in your app. Once they are initially set up the config_json file will be populated. From there you can change the alias names, query name, specify the specialtype (link, image, none) for fields. These are the things that don't seem to be saved in the WAB UI. You can also change the images to something more appropriate than the limited set you have to choose from as long as you use this code. You can also tweak the size of the image.

"resultsSymbol": {

"angle": 0,

"xoffset": 12,

"yoffset": 12,

"type": "esriPMS",

"url": "http://someURL/someimage.png",

"contentType": "image/png",

"width": 18,

"height": 18

MalcolmEchaluce

Robert,

Which config was it that we do these edits in? Previous versions of WAB (the Beta one) has the config in the Query widget already with some json in it. The current one only has the following:

{

"queries": []

}

Is this the correct config file we should be editing?

Thanks!

Malcolm

RobertScheitlin__GISP

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.

KevinHatch

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.

RobertScheitlin__GISP

Kevin,

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

KevinHatch

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?

StanMcShinsky

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

LeaDyrholm_Hansen

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.

MaryAnnSteinmetz

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

image001.jpg

NicholasBarger

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

TonyGroeneveld

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.

MaryAnnSteinmetz

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.

RobertScheitlin__GISP

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.

MaryAnnSteinmetz

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. ??

TonyGroeneveld

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.

LeaDyrholm_Hansen

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

RobertScheitlin__GISP

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.

LeaDyrholm_Hansen

I have the exact same question!

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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