Latest Contributions by DougBrowning

Update to show here is what we see in the server logs. It gets # as the layer input in these cases. line 1228, in ListFields return gp.listFields(dataset, wild_card, field_type) , line 378, in listFields self._gp.ListFields(*gp_fixargs(args, True))) OSError: "#" does not exist Hope that helps find it.

Found another quirk in the Analysis widget today. If you go from a popup then Set As Analysis input to a tool that uses a field list off that layer works fine. But if you use the Select widget, select a polygon, then do Set as Analysis input from there, then the field list will not populate at all. @Wei_Ying I think this is similar to the Search widget issue with the first popup. The tool is getting an input of just # somehow. We also see that if you have a popup from the last session up and come back later then try Set As Analysis input that will fail also saying the input layer is #. The user must reclick the polygon, get a new popup, then its happy. I am happy to show the team all these quirks if it will help (I have 10 now I think). This is a AGOL ExB. thanks a lot

Users request tool history in the Analysis widget but in reverse date order. I agree since it always starts at the top and you have to scroll down, sometimes a lot, to see the tool you just started. Reverse date makes more sense. This could also help with the other issue reported that the green running box here overlaps the running tool so you cannot actually see it run. That should be fixed also so that there no overlap here. Also I would really like a clear all history here. I have to scroll a long way now or remove one by one. And note as reported the tools are remembering defaults even across tools with the same options. I think the remember options could just be removed but for sure at least keep the defaults saved per tool not universal. thanks a lot

Analysis widget does not display messages from arcpy.AddMessage. This works in ArcPro and worked in WAB. It is making it hard to troubleshoot an issue I am seeing with Boolean parameters. thanks

If I remember you have to add a widget container then the widget inside of that.

@Wei_Ying We are also getting this in the server logs all the time when users try to use a tool. Again it seems to use the wrong credentials is my guess. Again our ExB is built in AGOL but uses services and custom GP tools from Portal 11.5. Error code: 403 Description: Access to this resource is forbidden, regardless of authorization. Message: You do not have permissions to access this resource or perform this operation. Thanks a lot

@Wei_Ying here is some more info. In the server logs the tools seems to just get a #? Again its only when you use the popup that auto comes up after a search with the search widget. We can recreate this every time on every layer we have, in every tool we have. Error executing tool. AIM Terrestrial Site Visit Summary Job ID: jb6f7302f25364574a65e0acd4682c847 : ERROR 000735: Indicator Layer: Value is required updateMessage Error: Traceback (most recent call last): , line 1228, in ListFields return gp.listFields(dataset, wild_card, field_type) File "C:\Program Files\ArcGIS\Server\framework\runtime\ArcGIS\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 378, in listFields self._gp.ListFields(*gp_fixargs(args, True))) OSError: "#" does not exist Thanks a lot

Thanks a lot For #1 on acting more like Pro. The big one there is how selections are used. In WAB if a feature was selected then the GP tool widget would see that selection just like Pro does. But in ExB it does not know anything is selected. This is true in a number of was to select from the select widget to the attribute table. I did a big write up on it here https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-analysis-widget/m-p/1626374#M19453 For #2 2. For your described problem here "It is generalizing polygons for display then uses these as the input to tools.": Based on my understanding, you are seeing different intersection point result in Pro and ExB analysis. Unfortunately I cannot reproduce using my own tool. We do need more details to work on this. We would highly recommend you contact Esri support so stuff can help you narrow down the problem provide a workaround if possible, and importantly provide develop team detailed information and repro steps that help team to investigate and fix. We appreciate your feedback posting on GeoNet which bring us quicker attention but for solutions we think it is better and more efficient actually give us a support ticket with details. We had a point right near a polygon boundary. If the user is zoomed out to see the entire polygon the point gets skipped on an intersect. If you zoom way in on the exact same polygon then that point does get included on the intersect. That tells me the polygons are being sent with a different vertex list on each run. I did see a UC demo that talked about this. I would check the ExB code there and see if it is in fact sending the client side generalized polygons to the tool. I am pretty sure if you ask the coder who did it they will see it. It should go get the full real polygon from the server and then send that vertex list to the tool. In Pro it is not generalizing so it all works fine. Hope that makes sense but I do think if you ask on the code you will see it. On #3 thank you for taking the time to read them! I am responding to each now. Some have gotten out dated enough that I no longer have a ExB sample to show you as we had to move on after a few months. Thanks again @Wei_Ying

Sorry we now gave up on the accordion since we could never get it to work right. So I can no longer test as this was back in Sept. But we have two other tickets open now that ExB is getting confused on which creds to use if we have a AGOL ExB with Portal data inside of it. We seen deny loops a lot. We see deny in the server logs also. One of those tickets is Case number #04081687. And the post is here https://community.esri.com/t5/arcgis-experience-builder-questions/embed-widget-fails-to-load-if-links-are-to-a/m-p/1663457#M21513 Again thanks a lot

Sorry let me try to explain better. I open up Tool 1 and check this option box here in blue I then open Tool 2 which has the exact same options and that same option box will already be checked. So it seems to cache the toolbox options by name and not by tool and name. So now any tool that has that same option name will default all the same. I hope that makes sense.

Sorry I do not know what this means? "Do you support the parameter groups (that can collapse/expand) that categorize the options? " Just an idea to support toolbox categories that work in Pro. Thanks

I was able to make a gif showing the issue. It still happens for us every time when coming from the search menu. If you re-click the popup then it all works fine. It is only that initial search pop up. It does it on all 8 of our custom geoprocessing tools that have worked for a long time. Again its just the initial search popup then set as analysis input Here are our settings Thanks a lot for looking into this our users get pretty confused.

If you are using count then once() can help otherwise as you scroll back it is recalculating the count on you is why. position(..) can cause infinite loops in some forms so if does that (it will give a warning at the top right of connect) use once(count()) instead.

Had some other team reach out to me just today that this is STILL an issue, which I am sorry is just insane. Esp since I have talked to each team in person face to face. Yet 5 years and counting. BUMP thank you

I think I have seen this warning from Esri before. It is generalizing polygons for display then uses these as the input to tools. I remember at the time I did not agree with that at all! I think what it does is the generalized polygon is client side so it grabs that and sends it to the toolbox when really it should go back and get the real vertices then send that to the tool. Should not be too hard to implement. When zoomed out it can be way off. We use these polygons to do an intersect on our point layer, then that selection of points in used in our reporting summaries. We just had a user find points being left out of a report. These reports are used to make important decisions and often end up in court. So these are a big deal! Its not a minor issue or bug. The funny thing is if we add the same exact polygon service to Pro and run the exact same analysis tool in pro it DOES find the point. So that tells me Pro has figured this out somehow. We really need ExB to act like other Esri software but it does not - and this has come up again and again. We have seen over the years that Esri teams are each are in their own silo. I get that, it happens to all of us, but it needs to start to be addressed. Again I ask that please someone from the ExB team can at least acknowledged they are seeing these posts as the list of issues just with the Analysis widget is really hurting our reputation. As listed here, just me alone has now found this many issues in just the Analysis widget. https://community.esri.com/t5/arcgis-experience-builder-questions/more-analysis-widget-issues-if-a-feature-is-found/m-p/1674410 https://community.esri.com/t5/arcgis-experience-builder-questions/more-analysis-widget-woes/m-p/1660577 https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-analysis-widget/m-p/1626374 https://community.esri.com/t5/arcgis-experience-builder-ideas/analysis-widget-support-for-toolbox-categories/idi-p/1619071 https://community.esri.com/t5/arcgis-experience-builder-questions/analysis-widget-hanging-with-a-spinning-run-in/m-p/1647330 https://community.esri.com/t5/arcgis-experience-builder-ideas/analysis-widget-add-support-for-parameter/idi-p/1619080 https://community.esri.com/t5/arcgis-experience-builder-questions/analysis-widget-hoping-for-enabled-false-support/m-p/1617567 https://community.esri.com/t5/arcgis-experience-builder-questions/set-as-analysis-input-will-open-the-tool-if-its-in/m-p/1635671 I understand all of us are busy, as am I I chasing all these down, but some of these are serious issues that should not get through testing and need to be addressed. Can anyone from the team please let me know if these are being seen or on the list. Some of these we brought up in person at the last 3 dev summits and with our rep also. I do not have the ability to make support tickets. Maybe @AlixVezina or @Jianxia ? Thank you very much!

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by DougBrowning

Re: Analysis widget cannot get a field list if the input comes from the Select widget

Analysis widget cannot get a field list if the input comes from the Select widget

Users request tool history in the Analysis widget but in reverse date order

Analysis widget does not display messages from arcpy.AddMessage

Re: Accordian Widget not accepting widgets

Re: Analysis Widget hanging with a spinning Run in Chrome only

Re: More Analysis Widget Issues - if a feature is found via the search widget Set as Analysis from that find popup fails as bad input

Re: Analysis widget is using generalized display polygons as input to the tools

Re: Analysis Widget hanging with a spinning Run in Chrome only

Re: More Analysis widget woes

Re: Analysis widget support for Toolbox categories

Re: More Analysis Widget Issues - if a feature is found via the search widget Set as Analysis from that find popup fails as bad input

Re: Show/hide qaqc questions Survey123 Connect

Re: Field Maps is creating lowercase GlobalId but AGOL does uppercase

Analysis widget is using generalized display polygons as input to the tools

Users request tool history in the Analysis widget ...

Analysis widget does not display messages from arc...

Re: Survey123 inbox query expression

Re: Show/hide qaqc questions Survey123 Connect

Re: Field Maps is creating lowercase GlobalId but ...

ArcGIS Arcade