Latest Contributions by NicholasBarger

I'm sorry... I must have confused you a little.  You care correct in the way it formats the different queries.  What I was getting at was in 2.1 I used contains and it behaved in a certain manor.  In the 2.4WAB / Widget it behaved differently.  My fix for the problem was to use the starts with operator and the contains query.  I had to change it in the code.  For some reason the contains produced strange results.  When I used starts with and the contains query it behaved like it did in 2.1 ... View more

Robert, Here is what I have found.  In the 2.1 version of the eSearch widget I used CONTAINS as the operator with this expression... "Upper(ADDRESS) LIKE Upper('%[value]%')" Now with the 2.4 version of the tool it appears I need to change the operator to StartsWith and then use this expression "Upper(ADDRESS) LIKE Upper('%[value]%')" to get the same behavior.  I'm guessing something changed slightly in the coding. I was able to work around it...but wanted you to know.  Here is an simple example of what I was seeing. I would search for 1100 N ATHERTON ST and my results would be... 1100 N ATHERTON ST 1100 S ATHERTON ST   Using the StartsWith and the same equation I get just 1100 N ATHERTON ST... which is what I would expect. ... View more

So I think I figured it out.  For some reason in WAB 2.1 when I used the operator contains it didn't give me the same results.  It appears that now I need to use Starts with to get the same results as before.  A little strange given the code between the two versions is the same. In any case, that solved my problems for the search. I also narrowed down the text box not showing up to the end users network restricting something...still not sure what it is blocking. ... View more

Good Morning Robert, Quick Question.  I have a couple users telling me they cannot see the text input box in the latest version of the eSearch tool... have you run into this before.  I've done the typical trouble shooting of having them clear their browser cache and checking all ports.  I'm wondering if their organization is blocking something that the tool needs for rendering the widget.  Thoughts? I have not been able to replicate this problem.  It works fine on phones and every other external device that I have tried. One more question.  This is something I noticed with the upgrade.  We moved from WAB 2.1 to 2.4 so I rebuilt the eSearch tool.  Anyways, when I search for 1100 N Atherton St in our buildings data I get multiple results... 1100 N Atherton St and 1100 S Atherton St.  Any ideas here?  I clearly enter N and not S, and the value would be 1100 N Atherton St.  I am using the "LIKE" operator in the query "Upper(ADDRESS) LIKE Upper('%[value]%')", Here is a public facing website... ArcGIS Web Application  Thanks in advance. Nick ... View more

I figured this out...it was a line that I changed.  I was changing all of my apps to https and the popup widget was breaking that.  So I reset the path for the images for the buttons.  I think I'm good.  More specifically I downloaded the images for the buttons from the internet and stored them within my network so they could also be https locations.  Then I went into the css/style.css of the popup widget folder and changed the location of the image file.  I had moved that file to another location. ... View more

I'm having a small problem with WAB2.1.  I have the popup widget in the side panel of the jewelry box theme.  For some reason the arrows that appear when you have multiple popups are not visible.  They are there and work but it is just white space.  You need to hunt around to find them.  Any ideas? ... View more

Hi Robert, I just got around to the Aloha Widget and everything appears to be working correctly.  Thanks again! ... View more

Great…thanks! ~ Nick ... View more

Here are the pas files… ~ Nick ... View more

Yes...when I look at the image in Aloha it stopped the chart at 6 miles.  So, the of the PAS image should be 6 miles in an app but it ends up 4.5 miles.  This is the test.pas file.  The other one I have attached test2.pas should be about 5.5 mile based on the Aloha image but ends up around 4.2 miles.  What I found was the image appears to be about 33% smaller than the image shown in Aloha. Here is the Image from Aloha Here is a picture from a test app that I created with no other layers except the ESRI Basemap. ... View more

Quick question Robert...I created my own PAS file and added it to your test site as well as my own Aloha test site with a measure tool added.  It seems that there is a difference in the scale between what Aloha gives in its chart and what the tool displays on screen.  In my example my chart maxed out at 6 miles.  When I added the PAS file to the widget in either website it came out at 4.5 miles.  I added the PAS file in the same location in your preview site as I did in our test site to make sure they appeared the same size.  We also measured the length in ArcGIS to make sure there was not a measurement tool issue. Any ideas?  I originally thought we needed our data in a specific projection, but both of our sites do not utilize any other data but the ESRI basemap. Thanks, Nick ... View more

Outstanding. Thanks for the heads up. As always we really appreciate the effort in creating / maintaining these widgets. ~ Nick ... View more

I think Hunter might be into something.  I've had this problem as well.  My fixes have been to keep a copy with the LL widget already set up but no app in the list.  When this happens I copy the clean version down and import the app back in to the WAB1.3.  The last time I was also able to copy the entire client folder over from the broken WAB to the Working one and that also corrected the problem. In my search for answers I looked into the //WAB/server/logs.appbuilder.log and found this error message... [2016-02-22 10:55:36.175] [INFO] server - No token is found, redirect /webappbuilder to /webappbuilder?action=setportalurl I also looked into the //WAB/server/db/apps file and at the end I was my test ones that failed and where they were being deleted.  When it fails it seems to not completely write into this directory.  One thing to note... my signininfo.json file appears to be correct. Given the fact that I found the error message with the no token found I would say Hunter's response is likely correct.  I just corrected this again yesterday before I found this thread.  So, if it happens again I will try this solution. ... View more

I responded to the incorrect message... see my message above.  I hope I have not misunderstood the problem in this thread. ... View more