Is anyone else able to reproduce this error?
Dan
Labeling is not possible due to limitations in the WPF architecture. We are working on a new version of Operations Dashboard that is based on JavaScript and will support labels (and many other things not previously supported).
Any timeframe?
Will this include labeling support for Operations Dashboard via Portal?
Adam Repsher- Public beta will be out shortly after UC and full release hopefully later this year.
Tiffany Selvidge- Yes, the portal release for the new dashboard will have the same functionality as the AGOL one.
This error persists with the latest version dashboard (10.3.4.1523), windows 10
The labels will not work in the desktop version because of the known limitation of it's framework. We encourage users who want to show labels to build their dashboards with the browser version in mind, or to switch to using our new Operations Dashboard, in which you can author in the browser. More details about that here and here.
Thanks!
Chris
Thanks Chris,
and another question
Thank you for the video, that certainly helps with troubleshooting the issue! What you are seeing here, again, it's a limitation of the WPF platform. It has no understanding of the javascript symbols or expression, so it uses default symbology on the map. Also, the legend works, only because it's fetching the image from your webmap. As you also saw, there was no problem in the browser version, because it's using the same javascript library as the webmap.
All of these 'platform' limitations have been addressed in our new beta app. If you haven't already, I would encourage you to join the beta and start building your own dashboards in the browser. We have seen tremendous feedback on it and look forward to the future of the product. Thanks!
Hi Chris,
I have been dealing with this bug for quite awhile. The Windows version of https://community.esri.com/community/gis/applications/operations-dashboard-for-arcgis?sr=search&sear... is at times the best application for our needs, but this bug and some others get in the way. I say bug because you have known that the JS symbol/expression has been a limitation for a very long time - enough time for a fix or workaround.
Moving forward, I was told over a year ago that this new JS browser version of OD would be the replacement that would fix all of my problems. Well, it hasn't yet - because it is still in Beta. If I build an app in this now, I will most likely not be able to use it when the Beta closes. It is also not supported as Production. You see my predicament. I am in the beta program, but I don't have much time to play, considering that I have spent the last month dealing with 10.5.1, three open tickets, one bug, and still no fully operational portal.
While I understand that the time spent moving forward to new products is important, we sometimes have to weigh that with time spent fixing the old stuff with bugs - especially if it takes forever to get that new product into production.
--Adam
HI Adam,
I can certainly understand your frustration and from working in technical support for 8 years here at Esri, I know how much even the smallest bugs can influence and disrupt customers. In this new Operations Dashboard, we want to get it right the first time, with many new enhancements and bug fixes from the old dashboard we've made along the way. There's a lot of platform limitations that we started running into with the WPF, and there was a clear need to move into a more fluid implementation that can easily adapt to changes in the ArcGIS platform, as well as the technology changes that come with maintaining software. We've had a lot of great feedback so far with the beta, and if there's things that we could do better, we definitely want to hear it. I would encourage experienced and novice dashboard users to take a look, and start building new dashboards, even if it's just to see what's changed and what we can improve upon.
Thanks,
Chris