Latest Contributions by DougBrowning

We have dozens of tables though not just one.  So we see no way for it to go to the one the user wants that is already in the table widget.  It just adds it a second time on us.   This worked fine in WAB do trying to match that. thanks ... View more

Have you found a way to just have it open the table widget if its already in the list of tables?  Add to table keeps adding it as a new one so then we end up with several.  Also when bringing in the table from Add Table it is defaulting to alphabetical field list order and not the order of the service (which we spent a lot of time on getting the way we want).   Thanks ... View more

Anyone ever figure this out?   I see here https://developers.arcgis.com/python/latest/guide/working-with-different-authentication-schemes/ that using gis = GIS("pro") is only the active portal but no way to switch that I can find. We have two diff AGOLs organizations and 12 different portals now.  So as an admin we often move data around but right here we get stuck.  We had used FeatureLayer in the past but we are seeing now that on long query's the token is getting left off the call so we are stuck now. Just like the other poster its all SAML logins so no un or pass even exist (not that I would ever hardcode a password). Thanks for any ideas. I would think it would be an easy add. ... View more

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

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

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

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

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

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

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

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

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