Latest Contributions by AmyKnight

Yes, that fixed the problem.   One reason that did not occur to me is that I checked the Query widget that comes with WAB and I can get the full list of 2,300 values there.  I assumed 1000 record limit in the service was more related to the number of records returned in the query result.  Thank you for the help! ... View more

HI Robert-  The excellent eSearch is working very well for us.  I just noticed something that I'm wondering if you might consider as an enhancement or guide me on how to adjust for our use.  We have one search expression based on a menu of unique values, where the universe of unique values is about 2,300.  The regular WebApp query tool would show the full list but the eSearch is limiting the list to the first 1,000 unique values.  Is there an option to get the full list?  Thanks for all your work on others behalf! Amy ... View more

Robert J, yes you can do that and Robert S has done it in his preview too, only he is using an icon as the link.  We use the link function similar to the way you describe.  It sounds like you want to use text so under the Search Links you just select the Link Type as Text.  Give it an alias, and enter the hyperlink field in the Link content.  It works great. ... View more

Stan-  Thank you!  It is helpful.  I am eager to learn everything I can.  I could see through inspecting that the .Pointer was the thing but was not able to find the css that contained it.  Now I understand that modifying the shape or size of the pointer does not help move the pop-up container.  Still,  I'll experiment with the code you've provided.  Thanks again- ... View more

Hi Brandon-  I was wondering if you figured out how to move the pop-up window or change the leader length?  I have tried to follow the suggestions here (among other things) but was unsuccessful, and I'm not an experienced developer.  Thanks ... View more

Nicholas,  yes, actually I did.  Similar to what you describe I had layers used for labeling that were duplicates of the primary symbolized layers.  I tried grouping the labels in my service as you describe and tested both ways. The grouping definitely fixed the problem.  The eSearch 1.1.6 results now display the attribute table with good performance and the full attribute tables for layers also perform well alongside the search result table.  Thank you! ... View more

I am having a similar problem.  But as soon as I hit the refresh button on the table the results come in. This has resolved it consistently so far.  ... View more

Thank you Stan!  I think I've got it-   I was just doing what you suggest following Robert's post above. ... View more

We also have a need to have Google Analytics tracking each time our WAB app is opened.  We have a web map application built with WAB for Developers 1.1 and recently deployed to our web server.  We have a snippet of GA code that goes into all our other web pages and I was asked to add it to the web map 'page'.  I am not sure where to paste it or best practice for doing so.  Any help would be appreciated!  ... View more

Yes, that was it! I thought I had seen something. Thank you- All my issues solved today! ... View more

Hello again Robert-   All my testing with eSearch today has been through WAB dev 1.1.  It is working perfectly there.  When I download and deploy to my own web server everything works great except that I can no longer get a drop down menu for my unique values searches.  I can still type in the search box (intended for menu) and get an accurate result, and all other searches included spatial and other attribute searches are working without a hitch. I thought i saw something previously about this on the forum but could not find it. Thanks for any help ... View more

This worked perfectly- Thanks so much! ... View more

Great, I will look for it. Thanks! ... View more

HI Robert-  the eSearch widget is GREAT!  Thank you for getting us over some major hurdles with query/search.   I was wondering about the ability to have the operational layer name (and attribute table tab name) be customizable to indicate that they are search results.  Currently they both use the layer name of the service.  In our case we expect the user to keep a statewide map layer of 'conservation lands' displayed but be able to search to return a subset of those features.  When that happens the Layer List shows the same layer name twice (Florida Conservation Lands in image below).  I would like to indicate that one of them is the search result.  My current workaround is to create a new service with identical layers, just named differently, e.g. 'Conservation Lands Search', for use with the esearch tool.  It is possible I have missed something.  Do you have any thoughts on another way to go about this?  Thank you! ... View more