Latest Contributions by DougBrowning

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 ... View more

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   ... View more

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   ... View more

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 https://community.esri.com/t5/arcgis-experience-builder-ideas/analysis-widget-does-not-display-messages-from/idi-p/1678456 https://community.esri.com/t5/arcgis-experience-builder-ideas/users-request-tool-history-in-the-analysis-widget/idi-p/1678478 https://community.esri.com/t5/arcgis-experience-builder-questions/analysis-widget-cannot-get-a-field-list-if-the/m-p/1678485  https://community.esri.com/t5/arcgis-experience-builder-questions/analysis-widget-is-using-generalized-display/m-p/1677142 https://community.esri.com/t5/arcgis-experience-builder-questions/one-or-more-layers-not-publicly-accessible/m-p/1627413 https://community.esri.com/t5/arcgis-experience-builder-questions/analysis-widget-fails-to-send-some-polygons-into/m-p/1690080#M22788   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! ... View more