Latest Contributions by JonathanKressin

  Hello, I wanted to check if anyone else has a situation where they allow a zero distance buffer on a selected feature.   I wrote a buffer tool for Web Experience Builder, and originally a user setting the distance to zero just captured all features within the buffered geometry.  However, since going live with this project, the call go GeometryService.buffer returns the following error: { "error": { "code": 400, "extendedCode": -2147220889, "message": "Unable to complete operation.", "details": [ "An error occurred during the buffer operation" ] } } I'm wondering if this is a bug in Server with our geometry service or if this is just a limitation on the buffer call.   Thanks! Jonathan   ... View more

In my Experience Builder mapping app (Developer 1.11), now that we are live, we are finding a problem with the search widget. In some address searches for valid addresses, the suggestion is providing good results, but clicking on them indicate that the address is not found.  If you just type the address and press enter, the address is found just fine.  Looking at the rest services being called, everything looks to be working right.  Where things seem to be failing is with the 'magic key' being passed from the suggestion.  I can reproduce the behavior from the rest endpoints by first using the suggest endpoint, getting the suggestions, and then pasting the address and magic key into the 'find address candidates' endpoint.  If I remove the magic key, the find endpoint has no problem providing a geocoded result. Has anyone else had this problem?  I am suspecting this is due to our using a composite locator and the magic key somehow not being matched up correctly.   Thanks! Jonathan   ... View more

I have created a new scalebar widget.  With it, when the user clicks on the scale bar, they can type in a new scale and the view jumps to that scale.  However, with an ESRI basemap loaded, this widget will only jump to a predefined scale closest to the scale that was typed in.  This is not ideal for the functionality of the application.   I'm trying to find a way to work around the predefined scales.  We only care about the basemap when we are zoomed out to the County level, but it is definitely nice to see the surrounding areas and not just have our County floating in space.  My widget works if I replace the basemap with one of our own layers.  I was looking at removing the basemap when zooming in past a certain scale (just hiding it doesn't help), but wasn't sure how to remove a basemap in Experience Builder once it has been loaded in. Any suggestions on  how to work around this behavior would be much appreciated. Thanks! Jonathan   ... View more

For ease of use, one of the features I really liked from AppBuilder was the popup dialog in mobile view for the widget controller.  That way, users had nice big buttons to browse thru and there was a lot less guessing on what tools were what.  It doesn't look like there is an out of the box way to do the same thing in ExperienceBuilder.  I did try to create a window and put the widget controller in that with labels and larger settings turned on.  Then had a button in the main app  turn view that window.   However, doing that breaks trying to use many of the widgets.  The displayed window does not go away when you try to use a widget so anything that interacts with the map won't work.   Has anyone found a way to reproduce this functionality in a usable way? Thanks! Jonathan   ... View more

I am currently working on my custom version of the Map Layers widget.  I am adding new actions that can be performed on the layer.  What I am trying to do is for specifically identified layers, allow the user to click on an info icon and display basic information about the layer.  I don't want to use the built in functionality and take them to the layer definition as it wouldn't benefit most of our users. I have the action displaying correctly and executing, but am having trouble figuring out the best way to display the information in a dialog.  My thought was to create a new dialog window in the builder, and then in the action execution code, display that window and use javascript to change the text in the dialog. However, I am trying to figure out how to control the dialog.  I can get to dialog information thru: const state = getAppStore()?.getState(); const dialogs = state.appConfig.dialogs; And I see there is an appAction.currentDialogChanged that I can run thru getAppStore().dispatch() If I am on the right track (which is debatable), I'm just not sure what I need to do with the dialog settings to indicate that it should be displayed.  And I haven't been able to find anyone else trying to do the same thing in EB.   Any suggestions on my approach or alternative approaches would be appreciated. Thanks! Jonathan   ... View more

With the release of the new search widget, I'm updating a 'parcel identify' tool I have created to handle selection messages from search to automatically perform a lookup on the search result.  I've created the action file extending AbstractMessageAction and have it responding to the search widget.  I'm trying to figure out how best to call the main identify method I have within my widget.tsx Widget class.  Most of the action code examples I see involves updating the widget's state.  I'd rather not take this approach if possible, as I'd rather just pass the x/y coordinates to the method that already knows how to deal with them and make the action as lean as possible. Any recommendations on how to access the widget's methods would be much appreciated. Thanks, Jonathan ... View more