Latest Contributions by patrickb

The workaround suggested by @DanteLee (and others) of using the AGO Assistant to switch the IDs of the webmaps being referenced. The key for producing correct/expected results with this workaround is to ensure that the webmaps have the exact same layers, and that each layer's schema is the same.    ... View more

  @MelissaWilliams1 We'd have to consider a search capability without having a map as a separate idea. If you'd like to pursue that as something for the community to weigh in on, might we ask that you submit a new post?  ... View more

@JamieLambert Thanks for continuing to lobby for this. We can re-consider our position and open the idea back up for feedback. Please note that adding an editing capability is not in our current product plans, and if we are able to the make the philosophical shift, it would be a while before we could bring even the basics.  In the meantime, we hope the workarounds offered can at least partially fill the needs.  ... View more

@ShorehElhami  It looks like you’ve included multiple ideas in this request, which doesn’t adhere to our Submission Guidelines. Can you please separate this idea into multiple submissions, one for each distinct request? This will help others in the community vote.  Some more info ...  Make it more responsive on mobile devices - This is in our current product plans.  Add print capability - We'll need some more details for this. Please be as specific as possible.  Category Selector -  This is in our product plan.  Header Panel - We can consider this if others vote for it.  Indicator - Please check our ArcGIS Dashboards Beta. I believe you can do this with Arcade.      ... View more

@MatthewBradbury Some of what you're trying to achieve can be done with url parameters and actions that respond to url parameters. Changing which field a data visualization uses to render itself at runtime (as opposed to edit time) is not something that is in our current product plans.  ... View more

@NorthSouthGIS In dashboards, we simply consume popups if they have been configured in a web map or web layer. You might be able to achieve what you're after via a workaround. One idea to try is to add the layer to the map twice. On one layer, set a filter to only show features that 'have attributes'. On the other layer, set a filter to only show features that 'do no have attributes'. Also on the second layer, remove the popups. In the dashboard, the count of all feature can be shown on an indicator element. When configuring the indicator, do not select one of the map layers mentioned above as its data source. Rather, click the Select Layer button and browse to the web layer that was used to create the map. It will not have any filters defined and will return an accurate count.  ... View more

@RobertThomas2 The dashboard layout system is quite flexible/powerful, and should allow you to re-create look you're after.  ... View more

@AmyWootton1  We've not seen that using our datasets and would need a reproducible case in-house before we could action anything. If this is an issue that is still happening with your data, please considering engaging with Esri's Support team as they are best equipped to handle things like this.   ... View more

@CrystalMcDermott1 If I understand correctly, I think this is already possible by following some steps.... The layers you bring into the Map Viewer should all exist as standalone web layers. One these layers, you can set the popup info via their item page. When these layers are brought into the Map Viewer, you can leave the popups as-is for all but one layer. For that layer, you should choose to Remove Pop-up (the Map Viewer is now 'overriding' what is stored in the layer)    When you add the Details element to your dashboard, do not select the layer that is stored in the web map (it no longer has popups). Rather, click the 'Select Layer' option and choose the original web layer (it's popups will still be there).  Let us know if this does not work.    ... View more

@RobbHodges Is the following along the lines of what you're trying to do? Here, the blue bars represent daily counts, the black line represents a rolling average, and the red represents a fixed guide/threshold. To create this chart, daily incident data had to be processed to create a new dataset that has incident_count and rolling_average per day as two separate fields. When configuring the serial chart, it used the 'Features' option, and a separate series was created for each of the incident_count and rolling_average fields. The incident_count series was configured to be blue bars. The rolling_average series was configured to be a black line.  If this is not what you had in mind, could you provide some more details?  As for the request for the indicator element .... Any chance you could submit as a separate submission for the community to vote on?  ... View more

@AlexBell Although we don't have any out-of-the-box ones to choose from, we've seen many great customer examples where multi-color SVGs have been used (on both indicators and dashboard headers). There might be an issue somewhere and this might be a situation where Esri's Support team can help.    ... View more