Latest Contributions by AlexisGreen

Sorry I was busy implementing it.  It works perfectly!  I have marked your answer as correct.  Thanks so much for your help!! ... View more

Looks like the folder shows up there only after you go in to configure the Search widget in the particular app you're working on in WAB.  It doesn't show up if the Search widget is just enabled but not configured.  Anyway I see it now.  Thanks!! ... View more

Thank you for the detailed directions.  I'm trying to implement this in the WAB Developer Edition, but cannot find a config_Search.json file in the folder of the particular web app I'm working on.  Is the file located somewhere else, or am I supposed to create it from scratch?  Thanks! ... View more

Thank you, but we had looked into this new feature and it is not quite what we are looking for.  While it does indeed limit the results to the current map extent, when you pan and zoom around the map, the tool limits the results to whatever map extent you happen to be at when you type in your search in the Search widget.  This has the effect of restricting the results too much when the user is zoomed into a small detailed area. In contrast, the behavior that we are seeking is for the extent that is used to limit the search results to be a fixed, unchanging extent, for example, an extent rectangle covering our county, that doesn't depend on how far zoomed in the user is in the map at any given moment that they are navigating around the map.  Anyone know if this is possible to do? ... View more

Yes we thought about using our own address locator, but prefer not to because of the reason you mentioned.  We are looking for something that forces the ESRI World Geocoder to restrict searches as you describe.  Perhaps the below documentation in the ArcGIS REST API: World Geocoding Service gives a clue.  Anyone know if I'm on the right track or how to do this in WAB? Search within an extent The findAddressCandidates operation allows spatial filtering of search results by using the searchExtent parameter. If you want to confine a search to a localized area, something that is especially useful in a mobile application, you can define a bounding rectangle to search within. No candidates outside of the rectangle are returned. Bounding rectangle coordinates can be entered as a simple comma-separated string in the format <lower left corner>,<upper right corner>. If the simple format is used, the coordinates must be in  the default spatial reference of the geocode service, which is WGS84. The searchExtent parameter can be used with all supported search types (street address, POI, admin place, postal code). ... View more

Thanks for your feedback. In planning a strategy, I was under the impression that modifying/extending the Out of Box Geoprocessing widget in the Web AppBuilder would be easier than starting "from scratch" writing a whole new custom widget, but perhaps not.  Anyone built a custom widget with parameter validation logic similar to what can be done in a Python script tool?  I'm leaning toward the JavaScript API for cross-platform support.  I would be very grateful for advice on how to get started doing this. ... View more

I have the same issue when I load my geoprocessing service into Web Appbuilder.  I configured the GP service to return a result map service, and while the map service is displayed in my Web Appbuilder app, there is no legend defining the symbology of the map service.  Have you found any answer or workaround to this problem? ... View more

Thank you - your explanation of the approach makes sense to me, in theory.   It sounds like you have a good deal of development experience.  As I'm more experienced writing Python tools that run in ArcGIS desktop, and a beginner at JavaScript web development, I need to learn how to make what you describe work, in practice.  The values in the choice lists can be hard coded.  Do you happen to have any tips on writing this type of validation logic, as well as how to make REST calls to the GP server, using the JavaScript API?  Perhaps that conversation should be moved to a different discussion area since it would not be about Python anymore.  I appreciate your feedback!            ... View more

Good to know.  The way the tool works in ArcGIS Desktop is the user chooses from a list of string values in the 1st drop-down menu, at which point the 2nd drop-down menu dynamically updates its choice list of string values depending on which choice the user picked from the 1st drop-down menu.  Could you give me advice or point me to documentation on how to do this validation in the JavaScript API?  Once the validation is done, I would need to pass the value that the user chooses from the 2nd drop-down menu as an input parameter to my geoprocessing model, which includes python script tools in the model.  The tool doesn't necessarily need to be implemented in the Web AppBuilder; I just thought that might be an easier way to do it than the API. ... View more

Thanks, Chris.  I wound up figuring out a different workaround using Python.  If I run the Merge tool from a Python script instead of as a tool added to the model, I can specify in the Script tool properties that the parameter is a Derived Output parameter (not a Required Input parameter), and when doing so, these characteristics of the parameter are retained when adding the script to the model.  For some reason, there appears to be no similar way to change these same characteristics of parameters in the Model properties, but rather only in the Script tool properties.  Again thanks for looking into it, but I think I'm good to go now with my workaround, as things are finally working successfully. ... View more

Chris, thanks for testing on your end.  I may not have been entirely clear in my explanation of the problem.  Looks like you did not flag the output of your Merge tool as a parameter, so it's not surprising that it doesn't show up in the model tool dialog when running the model as a tool.  I on the other hand intentionally specified the output of my Merge tool to be a parameter and also marked to "Add To Display", because I wanted to add the feature class to the ArcMap TOC, and I'm unaware of any other way to make data layers from models display in the TOC other than by making them parameters. To clarify, what I'm questioning is why the feature class that is output from the Merge tool is considered by ModelBuilder to be an Input, Required parameter rather than an Output, Derived parameter.  I'd prefer the parameter to not show up in the model tool dialog.  The only way I can see to make it not show up there is to make the parameter "Managed", which disables my ability to name the FC something more user friendly.  Perhaps this behavior is by design and there is no way to have the model both 1) not display the parameter in the tool dialog and 2) still allow me to name it what I want?  ... View more

The parameter I'm referring to is a feature class called "Type".  Even though it's the output of the Merge tool, ModelBuilder sets it as a Required parameter, so it shows up in the Model tool dialog as if the user needs to supply it as input. I'd prefer there only be one input in the tool dialog which is the "Potential Use" parameter.  Interestingly, when I mark the "Type" parameter as "Managed", ModelBuilder changes the parameter from Required to Derived.  This makes it not appear in the model tool dialog, but this is not ideal because it then won't let me change the name of the feature class, so when I mark it to Add to Display, it shows up in the ArcMap TOC with an odd sounding system-generated name rather than a user-friendly name that I would prefer.  Maybe there is no way to make the parameter Derived and still be able to control its name?  I plan to make this tool into a geoprocessing service in a web application, and would like for the user experience to be as easy as possible to use and understand. ... View more