How do I use the previous value for the reference in the Indicator? when I choose previous value it is displaying the same number. I have multiple entries in a related table associated to an event ( 1 to many) and trying to calculate the difference from the current and previous value.
I am also seeing this same behavior. Any insight would be appreciated.
Hello. Any hint about this issue? Thanks
Hello. Still no answer to this? It would be very helpful to see an example of how to use it. Thanks.
I think the Problem we're all facing is, that in an time based dataset the reference "previous value" is not referencing to the previous feature. Instead it is pointing to the actually feature.
Data
2020-03-28 | 15
2020-03-29 | 16
2020-03-30 | 17
I get 17 as value and 17 as previous value
Dear Derek Law, Dear ArcGIS Dashboards team, do you have any example for this - previous value? I am facing the same behavior, and I don´t see the usage for Previous value option in reference.
Thank you.
Hi Alisan,
> How do I use the previous value for the reference in the Indicator? when I choose previous value it is displaying the same number. I have multiple entries in a related table associated to an event ( 1 to many) and trying to calculate the difference from the current and previous value.
I am not clear on what you're trying to do; especially in the context of the related table.
FYI, when configuring an Indicator element > Data > Reference > Reference Type = "previous value" does not mean that it will reference the previous record in your data layer. It refers to the value/number displayed on the indicator before the last refresh interval was applied.
Hope this helps,
Dear Derek Law,
thank you so much for clarification. Just one more clarification. The refresh interval refers to refresh interval set on layer in WebMap in CDN cache settings in feature layer?
Thank you again.
Have a great day!
Hi Vladimir,
> Just one more clarification. The refresh interval refers to refresh interval set on layer in WebMap in CDN cache settings in feature layer?
Yes. For others who are reading this, please review this help topic for more background info on the CDN cache settings,
Build highly scalable dashboards—ArcGIS Dashboards | Documentation
Dear Derek Law, thank you very much!
Has anyone successfully gotten the indicator previous value reference to work right? It keeps giving the current value as the previous value. In my dash, I have data that gets updated once daily. When the data is changed (edited right on AGO) the indicator value changes. Unfortunately, so does the reference and it reports the new value as the previous value. I saw a bug out there about this and fixing it is listed as "not in the product plan".
I am using the public Johns Hopkins CSS COVID-19 feature layer which is in an indicator in an operations dashboard. I have the Active case as the value and "previous value" as the reference. I am trying to display the difference between the previous value and the current value. It only ever displays as 0. This feature layer updates daily but my indicator does not change. Is there another setting that I am not seeing?
Thanks very much,
@DerekLaw, is there actually a way to achieve what people are asking for here?
Ahh I see why I'm struggling.
The "previous value" reference is for if you UPDATE (overwrite) an existing record in the feature layer. e.g. If I had a single field "incidents_thisWeek" and I updated that value weekly, then the behavour of previous value would be as I'd hoped. However, if I have a database that has a date field for "weekstart_date" and then a separate field for "no_incidents" and I create (ADD) a new record each week, then the previous value feature doesn't work, because you aren't updating an existing record but creating a new record.
It doesn't matter that my indicator updates each week because I've set the max features displayed on the indicator to 1 and the sort by field to "incidents_thisWeek"
Thats confusing until you read this post! Thanks all.
So, now I know, how do I fix it?... My gut feeling is that this is going to involve the dreaded "Data expressions" feature... Very Powerful BUT not very easy to learn. Time to get on that learning curve.
Thanks @Nicole_Ueberschär & @DerekLaw
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
.png)
