Latest Contributions by NolitaLavoie1

‎12-17-2019

Just to note for the next person who might have this issue … I started from scratch and did get this to work as expected. e.g. Using an secure service has been added to my ArcGIS Online (AGOL) account using stored credentials and is shared with a group. Then using the Secured Service in Web Application Builder and the eSearch Widget. Then when the application is launched, only the AGOL account login is required for the eSearch to work. Not sure what caused the failure the first time. Haven’t been able to replicate. My hypotheses are: I did some updates and refreshes on the ArcGIS Server Map Service. AGOL may be finicky about this and this may have corrupted my secure link through AGOL. Made sure to use only the AGOL URL (https://utility.arcgis.com/...) for the eSearch url. The first time around I started with the original rest end point, which might have cached somewhere in the WAB dev. Made sure all my Secured Map Services hosted as “Map Image Layers” were shared correctly in AGOL. I also found an esri suggestion to only use hosted Feature Services. I did not have to resort to this for it to work. Thanks for creating such a superb eSearch Widget. It is a “must have” for any web map app in my agency.

‎12-13-2019

Did you ever get a resolution to this? I have the same workflow and the same issue.

‎11-13-2019

I thought the Survey123 Connect upgrade would fix the issue of changing basemap in the published Web Form. It actually made it worse, as the default is the TOPO which is the oldest and slowest of all the basemaps. Yes it allows for the user to change the basemap, but a simple form that public user (ie NOT people familiar with mapping) should not have to require this. I will be converting back to the older version of Survey123 Connect until this is fixed. And yes, i have to use Survey123 Connect instead of Web Forms because of additional functionality that isn't available in Web Forms that is in Connect.

‎11-15-2018

Did you ever get a fix for this? I had the same error message. This error only appeared when trying to set this email notification on a ArcGIS Server Feature Service registered through ArcGIS Online for use in Survey123. Since this Feature Service writes to an Oracle Feature Class, I will default to an oracle email trigger for this Survey123 notification.

‎06-13-2018

I am attempting to create a Web Mapping Application, using AGOL Web Application Builder, that automatically shows attributes in the attribute table. This works great, however, the attribute table does not seem to respect the visibility scale. If I zoom statewide, the attribute table will list every attribute in the map service, regardless if it is visible in the map extent. In my example below, this would mean an attribute table of over half a million points – not feasible. I have tried both my map service registered with AGOL (with scale range set in the mxd) and importing the data directly into AGOL for a hosted Feature Layer (with scale range set in the AGOL Web Map). I also imported into Web App Builder Developer. I see no out-of-the-box configuration to make the attribute table respect the visibility scale. What am I missing? Is this something that can be customizable to work? Example of flex app with attribute table not appearing until zoomed in to visibility range. https://maps.kdhe.state.ks.us/keif/

Online Status	Offline
Date Last Visited	‎11-11-2020 02:25 AM

My Ideas

Latest Contributions by NolitaLavoie1

Re: Referencing a secure search URL in the Enhanced Search Widget for Web AppBuilder

Re: Referencing a secure search URL in the Enhanced Search Widget for Web AppBuilder

Re: How to specify default geopoint base map in Survey123 Connect?

Re: A simple e-mail notification system for Survey123 for ArcGIS v2

ArcGIS Online Attribute Table and visibility (scale) range

Re: How to specify default geopoint base map in Su...