Hi all,
We are preparing for an upcoming 10.9.1 to 11.1 migration. We have some big Classic Dashboards and are still using Map Viewer Classic. We want to upgrade to the new dashboard format in 10.9.1 before we begin the 11.1 upgrade. Follow Feature functionality is not critical for us.
I am documenting the upgrade process but am unsure what steps to recommend as often the input maps (built with Map Viewer Classic) are also used for Web app builder applications.
esri recommended process:
The risk here is you can lose Map Viewer Classic functionality (that is used in your Web app builder).
I am thinking of recommending these steps:
https://portal.address.com/portal/apps/opsdashboard/index.html#/xxxxxxxxxxxxxxxxxa#mode=edit
Issues can be handled on a case by case basis with the first step of troubleshooting to check data sources in the old map viewer vs the new map viewer: Ensure that everything displays correctly and make sure that all layers that are used in your dashboard are visible.
We are probably overthinking it but unfortunately we took some complex dashboards and applications into maintenance without any supporting documentation. So I am trying to cover a process that will handle upgrading these too.
Any tips or lessons learned would be appreciated.
Solved! Go to Solution.
You may be overthinking it, honestly. All our old dashboards (even those tied to Classic web maps) came over just fine, even those that we did not manually save in the new Dashboards before upgrading.
Still, being proactive can save you and your users a lot of headache. Personally, I'd focus on steps 4-6 in that linked article. For each of your important dashboards:
This gets your dashboards into the new system. I've yet to encounter a situation where a Classic map configuration caused issues in the new Dashboard, but if such a thing happened, you'd know right away in step 5, and could, from there, open the map and make necessary adjustments. But where most maps will just work, steps 1-3 add a lot of unnecessary clicking and page loading.
You may be overthinking it, honestly. All our old dashboards (even those tied to Classic web maps) came over just fine, even those that we did not manually save in the new Dashboards before upgrading.
Still, being proactive can save you and your users a lot of headache. Personally, I'd focus on steps 4-6 in that linked article. For each of your important dashboards:
This gets your dashboards into the new system. I've yet to encounter a situation where a Classic map configuration caused issues in the new Dashboard, but if such a thing happened, you'd know right away in step 5, and could, from there, open the map and make necessary adjustments. But where most maps will just work, steps 1-3 add a lot of unnecessary clicking and page loading.
Thanks for the feedback Josh. Much appreciated.