POST
|
Unfortunately @KimberlyK, I'm still stuck. I'm certainly not happy to hear you are running into the same roadblock, but at least I know that I'm not alone! I find this issue to be THE primary limitation I have encountered in ArcGIS Dashboards and I really wish they would change this capability. I've posted this issue in several places in the Esri community and, so far, there has been clear best approach to solve this problem. I keep hoping that I can find a way to get the right person is Esri to understand this issue, and that once they do, they can make the necessary changes to eliminate this limitation. To some people this may seem like a problem only in the case of large and/or complex datasets, but that is not the case in my opinion. I have come up with ways around it when datasets and number of options are limited by making somewhat ridiculous data tables (for example, when creating this https://experience.arcgis.com/experience/cc8b79af0b754e2bab77522d4bc53df7), but that workaround is awkward and certainly not scalable.
... View more
2 weeks ago
|
1
|
0
|
83
|
IDEA
|
I still think this is a good idea and have some specific, tangible use cases (which I would be happy to describe, if/when it would be helpful). Fingers crosses that this comes to pass at some point! Cheers, Shane
... View more
03-21-2024
08:49 AM
|
0
|
0
|
355
|
IDEA
|
When an ArcGIS Dashboard element uses Categories from > Grouped values for data options, the source field menu is unable to be changed (it's grayed out) when referencing elements in the Dashboard driven by different data layers (for example, a different hosted table). However, the source field menu is able to be modified if the same data is used in an element which uses Categories from > Features. The result of this situation is that when using the Grouped values setting, the ability of element A to influence the element B is very limited if the element B is driven by a different dataset than element A. This is the case even if the two data sets have a field in common (different than the field used to display data in element A) which could be used to drive the action of element B, since the source field menu can not be modified to allow the action to use compatible fields in the two different datasets. The Grouped values option used to be more limited in the past regarding the types of map actions it could drive (like zoom, pan, and flash), but that limitation has since (happily) been removed. I'm hoping that a similar advance takes place for the ability to alter the source field when using this setting.
... View more
12-05-2023
04:30 AM
|
5
|
1
|
455
|
IDEA
|
I think this is a great idea! I had to get around this problem by creating two separate Dashboards and wrapping them in an Experience Builder (and then use some Arcade to translate). I am all for anything that makes this easier!
... View more
10-18-2023
05:31 AM
|
0
|
0
|
560
|
POST
|
When an ArcGIS Dashboard element uses Categories from > Grouped values for data options, the source field menu is unable to be changed (it's grayed out) when referencing elements in the Dashboard driven by different data layers (for example, a different hosted table). However, the source field menu is able to be modified if the same data is used in an element which uses Categories from > Features. The result of this situation is that when using the Grouped values setting, the ability of element A to influence the element B is very limited if the element B is driven by a different dataset than element A. This is the case even if the two data sets have a field in common (different than the field used to display data in element A) which could be used to drive the action of element B, since the source field menu can not be modified to allow the action to use compatible fields in the two different datasets. The Grouped values option used to be more limited in the past regarding the types of map actions it could drive (like zoom, pan, and flash), but that limitation has since (happily) been removed. I'm hoping that a similar advance takes place for the ability to alter the source field when using this setting. Until that happens, I am very open to any suggestions about workarounds to solve this problem. Thanks in advance for any advice! Shane
... View more
10-17-2023
12:31 PM
|
3
|
4
|
826
|
IDEA
|
@AndyGarwood - this is exactly what I want to do as well! I would love to create a link that would take a viewer from one ArcGIS StoryMap in a collection to a specific header in another ArcGIS StoryMap in that same collection (but keep them still within the collection). @OwenGeo - do you have any updates you can share on this topic? Thanks! Shane
... View more
11-16-2022
08:09 AM
|
0
|
0
|
912
|
POST
|
Hi @JohnSolly4! I agree with @MoyaCalvert_01 - I love using a bar graph to let users filter other content. The only way I can create the graph I need is by using grouped values. Can you provide any update on the fix to this issue? Thanks!
... View more
05-12-2022
08:09 PM
|
0
|
0
|
3355
|
IDEA
|
This is very important! The lack of Google Analytics capability in Experience Builder is one of the central reasons some organizations (in my case, in academia) are hesitant to embrace EB.
... View more
06-16-2021
08:53 AM
|
0
|
0
|
6736
|
POST
|
Thanks so much @Jelle_Stu_PR! That did the trick. I tried using variables to make it work in a bunch of different ways, but all approaches involved more than one return statement. Seems like you need to be more thoughtful in Dashboards (all Arcade code in one place) as compared to ArcGIS Online (where you can create and refer to many expressions, and where I saw the greatest number of examples to follow). Not only did your tip help with this Dashboard, it will undoubtedly help in many to come. Thanks again!
... View more
05-16-2021
01:08 PM
|
0
|
0
|
1210
|
POST
|
I have been working with ArcGIS Dashboards for the past year, but I finally decided to dip my toe into the world of Arcade this past week. I am trying to use Arcade to accomplish two tasks on the same ArcGIS Dashboards list: 1) look up the acreage of a parcel in a field and either show text "size not reported" or a formatted version of the acreage depending on the value (-999 indicates the size was not reported) 2) format the background color of each item in the list based on the access status of that parcel (values range from 1 to 5) After a bunch of googling and hacking away, I was able to produce code which accomplishes both tasks. However, only the first task displayed in the Advanced formatting winds up getting applied: It seems to me that something in my formatting is causing the reading of the code to stop at the end of whatever section of the script is on top. I tried looking at many examples that Esri and others provided, but I just can't figure out what is happening. I tried removing and adding brackets, but nothing I've tried has solved the problem. I realize that I am likely missing something simple, but I'm all out of ideas about how to troubleshoot on my own. Any advice / suggestions would be greatly appreciated! Thanks so much - Shane In case it's helpful, here's the code: if ($datapoint.ACCESS == 1){
return {
backgroundColor: '#BED7EA',
};
} else if ($datapoint.ACCESS == 2) {
return {
backgroundColor: '#DDBDDE',
};
} else if ($datapoint.ACCESS == 3) {
return {
backgroundColor: '#FFD9AA',
};
} else if ($datapoint.ACCESS == 4) {
return {
backgroundColor: '#aaaaaa',
};
} else if ($datapoint.ACCESS == 5) {
return {
backgroundColor: '#aaaaaa',
};
}
var acres = iif($datapoint.RSIZE<0, 'size not reported', Text(Round(Number($datapoint.RSIZE),1),"#,###.#"));
return {
attributes: {
realacres: acres
}
}
... View more
05-16-2021
12:13 PM
|
0
|
2
|
1236
|
POST
|
That's good to know! Thanks for responding. I haven't been able to find other mentions of this specific problem, so it's good to hear I'm not alone. I'll check out the bug. Thanks again.
... View more
02-24-2021
12:39 PM
|
0
|
0
|
718
|
POST
|
I have created a number of ArcGIS Dashboards (Beta) which contain embedded Survey123 forms to provide an easy way for non-GIS users in our organization to manage data collected by those surveys. Seemingly out of nowhere, none of the Survey123 forms are allowing users with the correct credentials to edit the data. Based on what I have been able to deduce (which might be incorrect, but...) it seems that the Survey123 form is no longer recognizing the credentials that the editors are using to access the Dashboard. Has something changed recently (in the past few weeks/month) in either Survey123, ArcGIS Dashboards (Beta) or web browsers in general which would block the passing of the login credentials necessary to access the Dashboard to the embedded Survey123 form? Or, if that's not the case, does anyone have an idea of what I could do to troubleshoot the situation? Thanks so much for any ideas or suggestions!
... View more
02-23-2021
02:22 PM
|
0
|
2
|
754
|
POST
|
Hi Zheng Liu - thanks for the update and tip! I just tested the survey using the ?version=latest method you mentioned, and it seemed to fix the problem I was having. I just rolled the survey to 3.10 and it seems to be working just fine. Thanks so much again! Shane
... View more
08-17-2020
07:45 AM
|
1
|
0
|
842
|
POST
|
Hi James, Thanks for your response! I am not one of the people at UNH who can create a ticket on their own. If you could create one for me, that would be great. However, I could always reach out to the few people at UNH who can create a ticket if need be. Thanks again, Shane
... View more
06-08-2020
11:47 AM
|
0
|
2
|
842
|
POST
|
Happy Thursday James Tedrick and Kylie Donia! Just checking back in with both of you to see if there is any update on this bug. Hope all is well with both of you. Thanks, Shane
... View more
06-04-2020
08:37 AM
|
0
|
4
|
842
|
Title | Kudos | Posted |
---|---|---|
1 | 2 weeks ago | |
5 | 12-05-2023 04:30 AM | |
3 | 10-17-2023 12:31 PM | |
1 | 08-17-2020 07:45 AM | |
2 | 05-15-2020 10:52 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|