How do you envision using Arcade in dashboards?

Question

The Operations Dashboard team has heard your requests to better support Arcade expressions in dashboards, and we want to know more. If this speaks to you, please complete this survey to tell us some details of how you'd like to use it in your dashboards. Your input is valued and will be considered. Thank you for your time.

https://arcg.is/19nPbv

Survey will expire Friday, April 12, 2019.

DavidNyenhuis1 · Answer

UPDATE: New Arcade support in dashboards has been introduced in the ArcGIS Dashboards Beta (recently renamed from Operations Dashboard). Please check out this blog article or the documentation to learn more.

AbinayaAS_0-1759329781864.png

ManishGohil_0-1759332093475.png

Anonymous User · Answer

Here is a example of an expression I need to do BEFORE summarizing the result in Charts and Indicators:

Sum( Contract_Cost_per_Acre / Contract_Acres)   across a Project, Region, or District.

Here's another example:

StdDev(  Volume_MBF_Acre /  Trees_Per_Acre )

The same kind of calculation issues apply to Source Fields that are _Avg

Taking the Sum of  Avg_BASAL_Area_AC  across multiple Contract Acres is problematic.

We need to be able to do real Math Calculations in order to correctly analyse and use our many years of collected Timber data.   In order to better manage our public Natural Resources.

Thank you -- for providing some Excel-like calculation capabilities, hopefully soon.

OHARNG · Answer

Also missed the survey.  At this time, looking to simply calculate a percent between two columns on the fly.  Versus having to recalculate an entire column every time a value is updated in any row in the database, or having to manually calculate a percent.  The percent would be displayed in the list in operations dashboard as it is in the attribute expression in the AGOL map.

I envision using auto-calculated Arcade based fields to automatically categorize data based on a number of other column values.  Can use it to automatically generate fields with different Units of Measure from the shape.area.

Sure I'll think of many more use cases as well.

Thanks for looking into this.