Latest Contributions by patrickb

Closing due to inactivity and lack of engagement by the community. This idea can be re-open with more details.  ... View more

Closing due to inactivity. The suggested workaround is still a valid approach to achieve a rolling average.  ... View more

Closing due to inactivity and lack of engagement from the community. This idea can be re-opened with some more feedback. As things are currently implemented, polygon features selected in a list can be configured to zoom a map. The extent of the zoom is the minimum bounding rectangle of the selected feature(s).  The rectangle is passed to the map, and the map itself makes some decisions in terms of the best scale / level of detail to render at, but the end result is that the selected feature(s) should wholly be displayeed.  ... View more

Closing due to inactivity.  An example of what a data expression might look like that 'preserves' categories after being filters might look something like the following. The result of this data expression could be the data source for a serial chart that gets its categories from 'Features'.    //Create an array of all the possible category values. var featSet = FeatureSetByPortalItem(Portal("https://www.arcgis.com"), "0047d80c5d144fa2b46b88320b008dd6", 0, ["OBJECTID", "DIV_NAME"], false); var stat = {name: 'Total', expression: 'OBJECTID', statistic: 'COUNT' }; var allCategories = OrderBy(GroupBy(featSet,"DIV_NAME", stat), "DIV_NAME"); //Create a filter that will mimic the scenario where some categories //are not present in the data being displayed on the dashboard var someCategories = OrderBy(GroupBy( Filter(featSet, 'OBJECTID < 141183'), 'DIV_NAME', stat),'DIV_NAME'); //The following should be ok on a small to medium number of categories. //Loop through all the categories. At each step, look for the corresponding DIV_NAME in the subset of categories to get the total var outFeatures = []; var outFeature; for (var allFeat in allCategories) { var div_name = allFeat.DIV_NAME; var total = 0; for (var someFeat in someCategories) { if (someFeat.DIV_NAME == div_name) { total = someFeat.Total; break; } } outFeature = { attributes: { DIV_NAME: div_name, Total: total }, }; Push(outFeatures, outFeature); } //Return a featureset return FeatureSet({ fields: [ { name: 'DIV_NAME', type: 'esriFieldTypeString' }, { name: 'TOTAL', type: 'esriFieldTypeInteger' } ], geometryType: '', features: outFeatures, });     ... View more

Closing due to inactivity and lack of community engagement. Can/will re-open with more details.  ... View more

Closing due to inactivity and lack of community engagement. Can/will re-open with more details.  ... View more

Closing due to inactivity and lack of community engagement. Can/will re-open with more details.  ... View more

Closing this one due to lack of new activity.   1) Dashboards has the ability to distribute the width/height of its rows and columns evenly (since December 2021).   2) The idea to be able to author dashboards at different resolutions should be submitted separately for stakeholders to vote on.   ... View more

Albeit perhaps a bit counter-intuitive, a table can be added to the map viewer and have a refresh interval set via its properties panel. Once done, the table then can be saved with the refresh interval 'burned in'. If that table is then used in a dashboard (via a map or as standalone table), it will be respected by the various elements (i.e. the dashboard will automatically check for edited data at the refresh interval and will update when necessary). If an alternate way of setting the refresh interval on a table is sought, please submit a separate idea.  Exposing a sort option on the table element for viewers to use is something we will investigate and consider for a future release.      ... View more

In the June 2023 update, dashboards now support a mobile view. Please note, only portrait orientation is currently supported.  ... View more

In the June 2023 update, dashboards now support a mobile view.  ... View more

Please review that what's new documentation for the June 2023 release of ArcGIS Dashboards.   See also community blog post by Dashboards team member @FriederikeAlschner     ... View more

With the June 2023 update of ArcGIS Dashboards (approx. June 14), we will make map selection workflows more intuitive. When layer actions are configured, dashboard users simply need to click a feature on the map to select it. There will no longer the requirement to activate a selection tool or to choose a layer when features from more than one layer are selected. The new click-it-to-select-it behavior is automatically enabled when layer actions are configured. If you (as the dashboard author) prefer giving your users the choice to select multiple features within a certain area, you have the option to add a rectangle selection tool to your map. To preserve the built-in map navigation (such as pan), this tool must be activated by the user before each rectangle is drawn on the map. Other new/improved functionality includes using the Shift key to add to a selection, and clicking an empty space on the map will clear the selection. ... View more