Latest Contributions by TaraHaynes

UPDATE: I have determined that my original assumptions that functions were causing this issue was incorrect. I have added updated info at the bottom of the post. Original: On the left-hand side is the pop-up in the Map Widget. On the right-hand side is the Feature Info widget, showing the pop-up as expected. All of the missing data/styling on the map widget pop-up was generated by functions within Arcade (in the pop-up in MapViewer), which is why I suspect them to be the culprit. Here is an example of one of my functions: function label (status) { if (status == "No Survey Data") { return "Not Surveyed" } else if (status == "No Nest Assessment Data") { return "Not Surveyed" } else if (status == "NA") { return "N/A" } else if (Find("Unknown",status,0) > 0) { return "Unknown" } else { return status } }   Here is how I am bringing these values into the HTML: var nest_row=`<tr><td style="padding:2px;"><b>${yr}</b></td><td style="padding:3px;border-left:5px solid ${bgcolor($feature[nestfield_name])}"><i>Discovered</i> - ${label($feature[nestfield_name])}</td><td style="padding:3px;border-left:5px solid ${bgcolor($feature[occfield_name])}">${label($feature[occfield_name])}</td></tr>`   Update: When I reference a field using a variable, as below, the value will not show up in the MapViewer pop-up: var fldname = "NestStatus_2016" return $feature[nestfield_name]   if the field name is called directly, as below, the value appears in the pop-up: return $feature.NestStatus_2016   If I reference the field directly at all in the script, even as a variable that doesn't get used, it will then show up in the pop-up where $feature[nestfield_name] is used. Which is to say that I have a workaround and my pop-up is functional, but I have to list every field I want to reference so that it can show up (this is a simplified version of what my script is doing): // referencing list of fields i need directly var flds = [$feature.NestStatus_2024,$feature.NestStatus_2025,$feature.NestStatus_2026] // calculating # of years between today and the year of nest detection var yrs = Year(Now()) - $feature.Year_Detected year_range = Array(yrs) tbl_rows = `` for (n in array) { yr = $feature.Year_Detected+n fld = `NestStatus_${yr}` tbl_rows = `<tr><td>yr</td><td>$feature[fld]</td></tr>`+tbl_rows } return tbl_rows   I know that 'year' fields are not great data management, and I hope to improve that in the future, but I suppose this is what I'm dealing with for now. Either way, this seems like it could be some kind of bug related to how the browser is loading pop-ups... interested to know if anyone else has run into this.   ... View more

I am working with data that has variable conservation targets based on the area of the landbase - eg. we need to conserve 10% of the total unit area. Currently, value guides only allow a static number to be input:   I would like to be able to at least input value from a field, eg.: Value = {Protection_Target} Having the ability to use Expressions/Arcade here would also be fantastic!   Currently, the only workaround I have found is to create a dot-style target point, but user feedback indicates that having a line on the graph would be preferred:   Preference: ... View more

I am developing an application that works best in Dashboards given the functionality of the filtering and charts available. However, I would like a functionality similar to Views in ExperienceBuilder, where an action (eg. setting a specific filter) could open a specific tab in a group of stacked items. I have tried developing the application in ExperienceBuilder, but the Filtering functionality in Dashboards is significantly more user-friendly, and I need to use Dashboards charts either way.   Reason: I recognize that this is a fairly small thing, and that it will only take a single click for a user to change the tabs manually, but it could be used to elevate the experience for users who are not confident or savvy with this type of technology!   Example: Data for this project is divided into different levels of spatial detail, from Region > District > Unit. I have stacked graphs to represent each level of detail: I also have filters set up for each level of spatial detail: I would like to have the ability to make the stacked items automatically switch to the "Natural Resource District" tab when something is selected in that filter. I imagine it could be available under "Actions"... in the same way you can use an Action to make a pop-up show, you could use an Action to make a specific tab show. ... View more

In Dashboards, there is a "Render Only When Filtered" option that can be applied when setting filter actions:   I would like to have this option available in ExperienceBuilder Message Actions - Data Filtering for all widgets (not just the Filter widget), specifically where that filtering is being applied to Lists, Feature Info, and Charts/Graphs.   ... View more

Hello!  Problem: My client wants to be able to filter framework data to a specific location either by selecting the data from a list, or by clicking that data on a map. However, the filter actions from the list and the map will conflict, leading to the framework data showing "NoData". Eg: Data is divided into Region > District > Unit 1. Client selects the South Coast Region from a List 2. List filters 'District' options to those within the South Coast Region 3. Client selects the West Coast Region on the Map 4. Map filters 'District' options to those within the West Coast Region - however, the South Coast Region filter is still being applied. Because no Districts are in both selected regions, the District list now reads "NoData".   Workarounds? 1. Data Selection actions seem to override each other, but this is not viable for my use case as I need the list to filter. 2. The Filter widget causes the same problem and is too limited for this use case as it can only act on its own source data. I am also using the lists as buttons to open different views, which Filter cannot do. 3. I have see the solution on 'Filter action from multiple widgets', but it is not applicable to my use case as the lists need to be within the same view; the user who submitted the solution also noted that it was not ideal. 4. Have user clear selection on List before selecting on the Map: not intuitive, particularly as this app may be consumed by users with limited technological experience.   Suggestion: When setting Message Actions, have a way to allow an override of previously-applied actions, particularly for data filtering.   Images: Action Settings on List: List: Filter Data Action   Action Settings on Map: Map: Filter Data Action   1. Selecting from Region List filters Districts (and highlights Map selection) 1. Selecting Region from List - filters Districts   2. Selecting from Map filters Districts, conflicting with filter applied in (1) and leading to No Data result 2. Selecting Region on Map - Filters List, conflicts with filter in (1) ... View more

Idea: The Bookmark widget is great for allowing different themes to be viewed on one source map. However, I would like to allow the user to choose their extent and view different themes within that extent, rather than the map zooming to the pre-set bookmark extent every time. Workflow context: Dataset: species data containing 7 themes; Natural Resource Region (NRR), Population Units (there are 5 within the NRR), Landcape Units (there are many within each Population Unit). Workflow: I want the user to be able to... View data at the NRR level, which works fine with current bookmark settings Select a Population Unit to zoom to, and view different themes at that extent without returning to NRR extent - does not work with current bookmark settings Select a Landscape Unit from a list, which will then open a new page with specific stats related to that Landscape Unit. I also want the user to be able to view different themes at the Landscape Unit extent without returning to the NRR extent - does not work with current bookmark settings Why Bookmarks vs. Layer List: I understand that the layer list would technically allow different themes to be viewed by turning layers/groups on and off, but in conducting user testing for this app, my users find this confusing given that the layers will cover each other - ie. it is not intuitive to them that layers higher in the list cover layers lower on the list. As this app is designed to serve the public eventually, I want to make it as user-friendly as possible. Having bookmarks would be much more user-friendly if the "zoom to extent" component could be toggled off. Other efforts to work around: Using a List to allow the user to zoom back to the Population Unit / Landcape Unit in question: since much of my app uses Selections to generate stats specific to a given Unit, this is not viable, because the list will unselect something that is already selected if it is clicked again. Map  Actions: I've tried setting map actions so that the maps will zoom to a certain extent, but the bookmarks override these actions 'Zoom to selection' option on Map Widget: the users do not notice or know to look for this option in user testing / I can't move it to a more noticeable place on the screen or really alter it to make it pop   My other option seems to be just making 7 different maps, which is probably what I'll do in the meantime. ... View more

I am embedding a dashboard in experiencebuilder via a URL. In this case, I am not using URL parameters. My issue is that the embed widget is reloading the dashboard every time I navigate away from the page or view and then return. This feels like it is clunky from a user experience perspective, as my users are often navigating between views to compare information and the reloading interrupts their workflow. I would like to suggest an option within the Embed Widget that would allow you to stop the widget from refreshing every time the view is changed. ... View more

Goal: having the ability to filter a Chart either by selecting feature on Map or scrolling to feature in Feature Info widget Issue: it does not seem to be possible to allow the user to filter chart both from the Map and from the Feature Info widget at this time Alternative solution: allow scrolling between features to be disabled on Feature Info Widget Configuration 1: Map Action - Feature Info - no Actions directly impacting Chart Expected behaviour: When record selection on map changes, either through clicking the map or scrolling through the Feature Info widget (which then selects record in map), Chart will be filtered Actual behaviour: Chart is filtered when feature is selected in map, but not when feature is 'selected' via scrolling through Feature Info widget   Configuration 2 Map Action - same as Configuration 1 Feature Info - Action set to filter Chart: Expected Behaviour: When record selection in Feature Info or Map changes Chart will be filtered Actual Behaviour: Chart is filtered when selected in Map, but gives INVALID CHART error when scrolling through Feature Info:   Configuration 3 Map Action - none Feature Info - Action same as Configuration 2 Expected Behaviour: When record selection in Feature Info changes, either scrolling through Feature Info widget or clicking on map, Chart will be filtered Actual Behaviour: Chart is filtered when scrolling through Feature Info widget, but defaults to no filter (ie. all features) when selecting record in map   ... View more