Latest Contributions by Wei_Ying

Hi @AndrewSpencer  if you are still seeing this issue, could you share the public app and we will take a look.  ... View more

@Tristan_Read thanks for your feedback. Unfortunately we were not able to repro on our end yet. Could you please contact Esri Support to share us more details about your app and case?  Appreciated. ... View more

@tshafer it looks like the user do not have access to the map data.  Would you check if the data sharing ever changed?  This banner only shows when the app contains resource requires credential.  ... View more

Hi @MackenzeOriger yes that is a known limitation. We will try to enhance.  ... View more

@JohnForne Currently yes a single chart widget only work with single layer. So if you change a different layer in the map, it won't act. You may try the workaround that Jose suggested above. But is using the same layer, the map extent change should trigger data action on the chart. You may share more details if that does seem to work for you.  ... View more

Thanks for your feedback. It is on our roadmap.  ... View more

Hi @DougBrowning, thanks a lot for your feedback and sorry about the problems you are encountering. Here are my comments:  1.  "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. "  We are sorry that you have such feeling. ExB's Analysis widget is actually not developed solo by EXB team. It use arcgis analysis components, which provides reusable ArcGIS analysis web components to build web analysis tools so it caters to the different needs of our internal customers like Pipelines, Map Viewer analysis , ExB, GeoPlanner and external developers. So that means we do try to sync up the behaviors across different products by using same components. But it also means ExB has the limitation to solve all issues at our paces (WAB gp widget is developed independently however so the team itself have more control).  But I do agree that we need more work to sync behaviors with desktop products like Pro. The analysis components are developed by a specific team which include exact team members working on Pro GP tools. So when you are seeing different behaviors, that is not because tools are developed by different team and logic. Desktop Pro tools and Online web service do have different standards and limitation. And the analysis components are still relatively new and they are growing. We would appreciate your feedback to help both ExB and analysis component improve.  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.  3. I reviewed all your listed posts and made sure all got replied. Again we really appreciate your feedbacks. We will try our best to solve these issues, and I have logged issues for the problems that I can reproduce based on your description. But the difficulties still exist in some issue repro cases. The beset way is actually working with support team who can help customers narrow down problems and also provide develop team clear repro steps if confirmed.  Thanks again, Wei ... View more

Hi @DougBrowning we do have logged enhancement request about this internally. It actually relies of analysis component team and we have raised attention to them.  ... View more

Hi @DougBrowning are you still experiencing this issue? I tested on the latest environment with Analysis widget inside of a Accordion, but cannot reproduce ... View more

Do you support the parameter groups (that can collapse/expand) that categorize the options?  ... View more

Hi @DougBrowning , Unfortunately I cannot reproduce from my end. How do you set search result as analysis input? Do you select the search result and from its popup - data action Set as input of Analysis?  ... View more

@DougBrowning Thanks for your feedback, I have submitted issues for these two: 1. "Users getting confused when they start a Analysis widget job they get a green check and think its already done." 3.  "But if we open one from the widget controller and one from the Set as they stack."  But I cannot reproduce the second problem "Also seeing if we set some tool options on Tool 1 then we open Tool 2 that has the same options - its somehow picking up the settings the user make in Tool 1 into Tool 2 automatically if the options match.  We really do not want this."   Can you share more details about this problem? Are you adding custom gp tools? In same Analysis widget or separate widgets?  ... View more

This is a limitation of your axis naming. X-axis always refer to category axis no matter the orientation.  We will improve.  ... View more

@MatsHardy your date format is dd/mm/yyyy, right? Which version are you working on? And do you use calendar-based for the time binning?   ... View more

Organizational theme is always not editable from Experience Builder. ExB can only read over the colors and map to the current app from your organization setting  ... View more