Latest Contributions by RyanKelso

‎11-20-2018

Thanks for giving me some ideas to try, Tanu. I see the following errors in the server log when I see the Get Layout Templates Info error in my app: Level Time Message Source SEVERE Nov 19, 2018, 4:18:15 PM Error executing tool. Get Layout Templates Info Printing/ExportWebMapSecured.GPServer SEVERE Nov 19, 2018, 4:18:15 PM Error executing tool. Get Layout Templates Info : Whitespace is not allowed at this location. Printing/ExportWebMapSecured.GPServer I don't know what to make of those errors. I can load the app the exact same way a dozen times and not get this error, and then might show up the next time, then go away after that. So hard to troubleshoot. I feel like I might have a better shot at trying to mod the Print widget to handle the error and repeat the Get Layout Templates Info request until it succeeds.

‎11-19-2018

Ok, what I found was status code 200 OK, with this response: {"error":{"code":400,"message":"Unable to complete operation.","details":["Error executing tool. Get Layout Templates Info"]}}

‎11-16-2018

I modified my layout templates and print service so when using the Print widget, and opening the Advanced menu, you have a nice sized "Comments" box for your own text, rather than the Author and Copyright boxes provided by the default layouts. This works great most of the time, but occasionally it reverts to the default Author and Copyright text boxes. I haven't figured out the circumstances or how to replicate the problem, so right now it seems kind of random and hard to diagnose. When it does happen, I see this error in the console: panel [widgets_Print_Widget_25_panel] created. WidgetManager.js?wab_dv=2.10:114 widget [widgets/Print/Widget] created. Print.js?wab_dv=2.10:193 Get Layout Templates Info Error Error: Unable to complete operation. at Object.m.load (init.js:1034) at init.js:88 at c (init.js:104) at e (init.js:104) at b.Deferred.resolve.callback (init.js:106) at c (init.js:105) at e (init.js:104) at b.Deferred.resolve.callback (init.js:106) at init.js:93 at l (init.js:108)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I am running ArcGIS Server 10.5.1 and WAB 2.10. I thought the problem could be related to instances of my print service going idle, but I have it set with a minimum of 2 instances running. Any ideas on how to fix this?

‎11-06-2018

Thank you Robert! I guess a couple of people in our office have a workflow where they were running into this pretty frequently. They will be really happy now. Works great in WAB v2.10 by the way.

‎11-02-2018

Robert, we've found an issue with eLocate's address inspector and popups for other layers. We use eLocate with the "Keep address inspector tool active after each address inspection" option enabled. So if you use the inspect address tool, then close the eLocate widget, then try to click a feature on the map to get its popup, you get nothing. What I see happening is when you close eLocate, it deactivates the address inspector tool as it should. But if you open eLocate again, you see that although the address inspector tool is not active, the button for the tool still has the appearance of being active. It seems that as long as the button appears active, popups on other layers will not work even with eLocate closed. Deactivating the button by clicking it or switching to the Address/Coordinates tabs solves the problem.

‎10-29-2018

We recently discovered this issue with invalid address suggestions and it is a bummer to have to decide between potentially misleading/confusing users with blatantly incorrect information vs. disabling a feature that can be genuinely helpful. It's hard to believe that they decided it was a good idea to roll out the suggestion feature without at least some kind of validation performed on the address numbers. I must have loosened the minimum candidate score and spelling parameters so much that we don't see 'No Results Found', but you can end up with a very unexpected result in comparison to what the suggestions were indicating. I definitely support this idea of eliminating suggestions for addresses that don't exist. It's poor implementation. Some kind of "address number out of range" message could be helpful to inform the user of the problem because as much as I don't like how the suggest engine works, the user does have some responsibility for plugging in bogus addresses, or reporting the problem in the case they've found an error in the address data.

‎10-29-2018

Similarly, I wanted to have URL search parameters with eSearch available for some scenarios, but I didn't want to open the widget on the initial app load. Our preference was to have the Layer List or no widget at all display initially. My solution was to use the URL parameter that loads the app with an alternate config, which would be setup to load eSearch at start. Here's how it would look: https://gis.lewiscountywa.gov/webmap/?config=alt-configs/esearch.json&esearch=003767000000&slayer=0&exprnum=0 I also like that you can add &close=true in case you want to simply want to zoom to a search result and not display any additional content.

‎09-20-2018

Hey Jack. I do get the same thing... an ugly developer console full of 404s for every resampled tile. I don't like it. I try not to look. Since the feature technically works fine despite the errors, I haven't dedicated any resources to finding a fix... if one even exists. If you find anything, please let us know!

‎08-07-2018

A ribbon bar type of UI is a great idea, especially having it mirror the look of Pro. I came across a Geocortex app where they had done this.

‎08-07-2018

This feature is right at the top of my wish list for Web Appbuilder. I've seen it in custom implementations of WAB and in other configurable web app products.

‎08-06-2018

Tom, I have to pop in here from time to time to reiterate that this widget rocks and thank you for sharing it! I occasionaly have users tell me how they really like it and of course I am happy to defer the credit to you. I have a couple of very small nuggets to throw into the idea box. The first is that it would be cool if the "Show Bearing" option worked for the simple line geometry type in addition to polyline and polygon. A couple of people who are maybe not as savvy about geometry types have been confused over this. The second thing is that I noticed if I make some measurements and then create a PDF with the Print widget, then text color/size/rotation doesn't carry over to the PDF. This is really minor and I only just noticed it, it's not even something that any users have brought up. In other words, no big deal if it's not something you have the time to check out. Also, I have upgraded my app to WAB v2.9 and your widget is working trouble-free.

‎07-26-2018

Thanks for the reply George. I'm not really worried about anything in particular, just potential issues I don't know about. Maybe there aren't any. It "SEEMS" like deleting all the features then re-loading them should start the OID's back at 0, so this is mostly just me being OCD I guess.

‎07-26-2018

I have "Edit" and "Publish" enterprise geodatabases (SQL Server 2014) with a one-way replica from Edit to Publish. Some feature classes are maintained by users with their own copies in other locations (file gdb, .shp) so I have a script that finds updated copies, runs Delete Features / Append to update the Edit geodatabase and then Syncronize Changes to update the Publish geodatabase. This process will not reset the OBJECTID's back to 0, so they will continue to accumulate every time I run the process. I don't know if this will be a problem in the future or not but I don't really like it. Is there a way to get the OBJECTID to reset to 0 in this process without having to unregister the feature class as versioned (to use Truncate), which I think would also require me to re-establish the replica? Running a "compress database" after Delete Features didn't work.

‎05-14-2018

I can message the url to you so you can check it out. I think you have to follow me to allow private messages though. I didn't assess the file size difference. Running your own test on a small area would probably do a better job of answering your questions

‎05-10-2018

Yes I have tested and compared tiles using <Antialiasing> as true and false. Setting it to true definitely enforces some degree of AA. It may be in the eye of the beholder, but to me it is a significant improvement over no AA at all. I think it could be better though, hence the point of this thread.

Online Status	Offline
Date Last Visited	‎07-01-2025 08:41 AM

My Ideas

Latest Contributions by RyanKelso

Re: Occasional problem with custom text in Print widget

Re: Occasional problem with custom text in Print widget

Occasional problem with custom text in Print widget

Re: Enhanced Locate Widget Version 2.16 - 08/21/2020

Re: Enhanced Locate Widget Version 2.16 - 08/21/2020

Re: geocoder Suggestions list in Search should not contain addresses that don't exist

Re: Enhanced Search Widget Version 2.13 - 09/25/19

Re: Why do ESRI Basemaps show pixelated tiles at LODs 20-23 but my services don't

Re: ArcGIS Pro theme for WebApp Builder

Re: Search/Filter option in LayerList Widget

Re: Measure Widget 2.15 for Web App Builder

Re: Delete Features - Reset OBJECTID?

Delete Features - Reset OBJECTID?

Re: Manage tile cache, anti-aliasing

Re: Manage tile cache, anti-aliasing

Re: Expressions Not Being Honored By The Append To...

Re: Delete Features - Reset OBJECTID?

Re: Manage tile cache, anti-aliasing

Manage tile cache, anti-aliasing

Re: Cached map service without Server access to da...

Web AppBuilder Custom Widgets