Latest Contributions by TaraHaynes

I have a convoluted workaround involving the List widget... I know the List widget used to autoselect the first record upon opening the app, which was nifty, though it doesn't seem to do that any more / I can't figure out how to do it again. However, it can still be used in a different way.  1. Create a Section. First 'View' is a List widget, second 'View' is the survey embed. Use the URL parameter for the survey embed, as mentioned in the original post. 2. For the List Widget: In 'Action > Message Action', add a trigger for 'Record Selection Changes'. Select 'Framework'. 'Trigger Data' should be the feature you're selecting in the map, and 'Action Data' should be the feature that is informing the Embed widget. These will probably be the exact same feature (so they will be auto-bound), but if not, they should connect on the 'GlobalID' field. 3. Add a Button to the List Widget to link to your second / Survey123 view. Style the rest of the List Widget as you like - I used this as a way for users to check the data of the point they selected before editing, and labeled the Button as "Edit Information". (I no longer have access to the app I built for this post, but this is the idea:) 4. When the user clicks the button, it should take them to a loaded Survey123 view, since clicking the item on the List selects the associated record across the framework. 5. Make sure you have a button on the second View to get back to the list! The only downside is that if the user clicks the map while in the Survey123 view, it will unselect the feature and throw the error again... usually I put text like 'Select Point on Map to Edit' above the Survey123 widget, just in case. Hopefully that helps... it's the best I've come up with, though hopefully ESRI is working on a way to auto-select the first record or something because so many of their widgets have this issue with looking funky before things are selected! If you find a better solution, too, please let me know! ... View more

@Anonymous User Thank you! I was very happy to see the update, fantastic stuff happening in the Arcade world! ... View more

@EmmaHatcher  If you are not using Arcade expressions for your pop-ups, ExperienceBuilder has a lot of ways to dynamically display content without having to rely on the Feature Info widget. To make a "version" of the Feature Info widget, for example, you can connect a Text Widget to your data and use the Dynamic Content option to read data from the dataset. The limitations are that you cannot use complex Arcade expressions or directly edit the HTML when working with dynamic content (the latter may eventually be available with the Embed Widget), and it might look wonky when nothing is selected... but this could solve some of the problems with displaying content differently from the pop-up, at the very least? The List Widget is another option that gets around the "things looking wonky" problem. Not perfect solutions, but hey. ... View more

@ShengdiZhang I am having an issue where if I disable pop-ups in this way, one of my maps will no longer allow me to select features, thus preventing the Feature Info widget from operating as it should.  Strangely, it is only happening on one of my maps - the rest allow me to select features when pop-ups are disabled. Do you have any ideas why this might be? I am trying to trouble-shoot, but having little luck... the configuration/settings of the different maps and hosted feature layers are the same.   EDIT: I figured it out; it's because the layer I was trying to select was stored in a group in the new MapViewer. Once I moved it out of the group, I was able to select it (and populate a Feature Info widget) when pop-ups were disabled. Must be a bug around grouping? ... View more

Well, that was a simple solution! Thank you for the response - I'm currently on emergency deployment and some extra brain power is much appreciated! ... View more

Thank you for the input - I agree with this, and have had the same experience as far as the selection obstructing the user view / clearing the selection being unintuitive. ... View more

@PaulBarker  Coming to this thread with the same issue as the other users.... do you know if there are any plans to implement this before the end of the year? Thanks! ... View more

Hi, thank you for the quick response! The source order appears to be fixed! However, I am still getting the initial dropdown, which filters the map upon click, and then a second drop-down that I need to click in order to 'select' the feature. It looks somewhat different, so I have updated my original post in case it helps. I tried clearing my browser cache in case that was causing the issue to persist - let me know if there are any other steps I should try if it seems the problem is on my end! ... View more