topic Re: esearch 1.1.1 not able to return results in Web AppBuilder Custom Widgets Questions

esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 16:40:51 GMT

I am getting the following error and the search button is not displaying in the widget. Don't know whether this has anything to do with it.

Now I can't even do anything in the new widget since the search button is gone.

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Fri, 27 Mar 2015 17:29:27 GMT

Mark,

That error is pretty standard for servers that do not have CORS enabled so no that is not the issue.

What version of Web AppBuilder are you using?
Have you tried to create a brand new site in WAB and then add the eSearch widget and configure a layer (for testing)?

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 18:57:16 GMT

I am using the latest developers edition 1.1. That worked creating a

brand new application in the latest version.

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 18:58:47 GMT

I was hoping I would not have to rework everything, I used the upgrade option with my old app. For some reason it will not work in the old app.

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Fri, 27 Mar 2015 19:07:22 GMT

Mark,

Were you just coming from version 1.0? I have not seen any issue with people upgrading to 1.1 so far.

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 19:11:40 GMT

Yes. Its like something is not clearing out behind the scenes. I have

cleared my cache numerous times, Restarted the app builder, and every time

I add the new esearch to an existing app it does not show the search

button.

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 19:36:14 GMT

Ok so the search button is there, but you cannot see it in the Tabbed Theme. I can click in the area that it should be and it will run a search, but you cannot see the search button. Would this be something with the UI.

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 19:43:28 GMT

I think I am getting somewhere, for some reason the search button is not

picking up my custom style color. That is why it is white and the text is

white so it will not show up. Do you know why this may be?

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Fri, 27 Mar 2015 19:55:52 GMT

Mark,

Yep, I guess I forgot to account for custom theme colors.

Just add this to the style.css for the widget.

.TabTheme .search-btn {

background-color: rgba(89, 102, 121, 1);

}

.TabTheme .search-btn:hover {

background-color: rgba(89, 102, 121, 0.7);

}

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Fri, 27 Mar 2015 20:58:39 GMT

Mark,

Version 1.1.2 addresses the button css issue by defining a default button color if some one is using a custom theme color and another issue reported from another user.

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 27 Mar 2015 21:06:52 GMT

Re: esearch 1.1.1 not able to return results

MarkYerington — Mon, 30 Mar 2015 12:39:28 GMT

Thanks Robert. That was it.

Re: esearch 1.1.1 not able to return results

MarkYerington — Thu, 23 Apr 2015 18:34:28 GMT

I am getting the search failed error again with a 400 bad request with version 1.1.6 and version 1.1 of the web app builder. This time I try to create a complete new app and it is still not working with any layers on my server.

Any ideas why this keeps happening.

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Thu, 23 Apr 2015 19:22:58 GMT

Mark,

Does your app happen to be public yet?

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 24 Apr 2015 12:13:06 GMT

I attached an image, of the console error. I hope it came across. It

shows the query string, but after that throws the 400 error.

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Fri, 24 Apr 2015 12:16:06 GMT

Mark,

Unfortunately this is not enough info fro me to do anything with. Is your app public yet? If not can you download the app and send it to me?

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 24 Apr 2015 12:29:18 GMT

http://magic-gis.com/error/

Its out there now. Try a 0826352026 pin search.

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525

Re: esearch 1.1.1 not able to return results

RobertScheitlin__GISP — Fri, 24 Apr 2015 12:39:07 GMT

Mark,

You can not combine https and http in the app. Your App URL is "http://magic-gis.com/error/" and then you use "https://magic-gis.com/arcgis/rest/services/MAGIC_Landbase/MuscatineParcels/MapServer/0" in the eSearch config.

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 24 Apr 2015 12:40:07 GMT

An invalid where clause or definition expression has been requested:

"(Search for Parcels AND Upper(PIN) LIKE Upper('%0826352026%')) AND

(Upper(PIN) LIKE Upper('%0826352026%'))"

This is a severe error on the server. Seems like a bad query expression

is being sent.

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525

Re: esearch 1.1.1 not able to return results

MarkYerington — Fri, 24 Apr 2015 12:43:07 GMT

Even when I make a request with https it still fails though.

Mark Yerington, GISP

MAGIC GIS Systems Analyst

3205 CEDAR ST | MUSCATINE, IA 52761

PH: 563.262.3316 | CELL: 563.260.4525