Latest Contributions by deleted-user-dbQhBq-o3nyM

Andrea, I originally was testing the issues you were having on a map layout of 8.5 x 11. I was able to duplicate the problem you are having when I changed the page layout size to 36 x 48 and stretched my PNG to a very big size. The logo I was using then became pixelated and there was nothing I could do about it. I changed all the settings I could see and still nothing changed it. ... View more

I'm not sure why that would be. It has worked great for me in the past. What is the DPI set to under the General tab when you export the map? You might also look at the format tab and experiment with those settings. I'm not sure what I have below is the "correct" way to have it set up, but it typically has not given many any issues in the past. ... View more

Robert, Thank you. I don't know who thought that it was a good idea to add an ampersand to our zone abbreviations. Obviously they were not thinking the way the computer does. I suppose I will wait until the release then. Thanks again. ... View more

Robert​, was this ever addressed in the latest release? ... View more

Robert, regarding your question above about running WAB in https, how do I set it up any other way? I just downloaded WAB, registered the app, then started creating my app. It may be a dumb question, but I don't know any other way. I know enough to mess things up, but not enough to fix it. So as can be expected, I can only load secured rest services into the app. Slightly related, I got eSearch to work on most of my rest services; however, when I set up the Expression Value to query my county zoning rest service, it just says processing and never finds the uniques for the field (0 of 2712). Does this have to do with me using secured protocol?  Or why would it give me the "ESRI (processing) Wheel of Death"? The weird thing is, I ran the exact same set up in 1.2 and it worked great. ... View more

Not a reason, just new to creating these custom webapp builders as of last month. Just a rookie is all. ... View more

I deleted the app again, then I cleared my cache this time, and downloaded the eSearch 1.3. I got the above errors and warnings in my browser console. But I got it to work this time. I was just grabbing the rest service as anyone can by clicking on the layer list, then looking at the description. I saw the error above and tried going through Server, copied the rest services from my inside URL and it worked. Thanks for taking the time to help me. I We really appreciate the work you have done to create these custom apps. You do amazing work! ... View more

I downloaded the app from here just last week: Enhanced Search Widget Version 1.3 - 12/14/15​ many times, then deleted, and tried again. Here is a screen shot of the version: ... View more

I'm having trouble creating my expressions in eSearch 1.3. Every time I go into Update Expression Value, below is all that shows up: The fields to search on aren't coming in and I can't choose how the search should be performed. Also, I can't add links in 'Link Content'. I could do both in the last version 1.2.x. ... View more

After downloading node.js and running the update, then deleting and recreating the signininfo.json, I was able to update to 1.3 and it works. Thank you all for the feedback! I appreciate it. ... View more

Mark, I've checked the signininfo.json file and it has the correct appid. Everything looks good there. ... View more

Matthew, According to the instructions, I am to open the command prompt in the folder of the newest version then type the 'node upgrade' as well as refer back to the old version, but every time I do it tells me 'node' is not recognized as an internal or external command. ... View more

I have not. I tried searching for that sort of thing, but could not find it. Thanks ... View more

I was able to get it to work by setting the field to Predifined Value "Unique", but using the Predefined doesn't work. Thanks for the quick response!!! You make some awesome widgets!! ... View more