Upgrading to Version 2 of Communications Data Management
This blog explains the process to upgrade from Communications Data Management (CDM) version 1 to version 2. If you’ve previously deployed CDM, you are not required to upgrade to version 2.0. You should only upgrade if you will benefit from the new capabilities and the benefit outweighs the effort.
It is also helpful to understand that you are not performing an update to your currently deployed CDM solution. Instead, you are deploying the latest version of the solution into your ArcGIS organization and then loading your data to the new version.
Background
This freely available ArcGIS Solution can be used to map coax, copper, fiber, and wireless system assets, edit data, view system maps in the field and office, view asset reports, and collaborate with map notes. This solution was previously known as Communications Data Management for ArcGIS Online But was renamed to Communications Data Management at version 1.1.
The first release of CDM was in November 2020, with a major update to the solution released March 2023. We updated the solution to include the ability to manage serviceable locations and additional management of service areas. The version 2.0 update enables user to enhance their understanding of current and potential future customers. Additionally, minor bug fixes were resolved to improve the solution. Additionally the newly released Communications Service Availability solution is aligned with the CDM version 2.0.
Upgrade Process
We suggest this process to upgrade an existing Communications Data Management implementation to Version 2.0.
- Deploy version 2.0 of Communications Data Management to your ArcGIS organization
- Determine whether your existing deployment is in an out of the box state or has been modified post deployment
- If necessary, add your modifications from your previous deployment to version 2.0
- Load data from previous version to version 2.0
- Add users to appropriate new groups
- Provide new apps to staff
- Remove previous version
Step 1 Deploy Version 2.0
If you have not deployed version 2 of CDM yet, do this through the ArcGIS Solutions app in your ArcGIS organization (the ArcGIS Online account or ArcGIS Enterprise Portal you are currently logged into). The ArcGIS Solutions app will automatically deploy the current version of the solution if you are deploying to ArcGIS Online or ArcGIS Enterprise 11.1 and beyond.
When you deploy, make sure to set the spatial reference the same as the spatial reference from your currently deployed solution.
The ArcGIS Solutions app will NOT write over an existing deployed solution with a new version of the solution. This is important to avoid the potential for loss of data or loss of modifications to maps and apps.
During deployment, the ArcGIS Solutions app will create a new folder in your ArcGIS organization and deploy the items (services, maps, views, app configurations) for the solution. If you currently have version 1.0 -1.2 deployed in your organization; the following items from a 1.0-1.2 deployment will be used for your version 2.0 deployment. The ArcGIS Solution app can use previously deployed items to power a new version of a solution if the items did not change between versions.
- CommunicationsMapNotes– Feature Service
- CommunicationsMapNotes_editing – Feature Service (View)
- CommunicationsMapNotes_managing – Feature Service (View)
After deploying version 2.0, the items above will need to be moved from the previous version’s folder to the folder of version 2.0.
Step 2 Gather Information About Your Current Deployment
After deploying your current Communications Data Management solution if you did not modify any of the items deployed with the solution, then your deployment is in an out of the box state. You are ready to load data into version 2.0!
Did you further configure it or customize it? If so than it is not in an out of the box state. If you added any attributes to the feature layers, modified domains, modified the maps, modified dashboards, or the like, and you want to keep those modifications after moving to the new version, then you need to do the same modifications to the corresponding items in your version 2.0 deployment before you load your data.
Step 3 Load Data
Version 2.0 has a Serviceable Location layer and updated attributes for the service territory layer; you will need to review the new schema to the version 1 schema and then load it.
The most efficient way to do this is using the Data Loading Tools. You can get the Data Loading Tools and the documentation on how to use them here.
If you are unfamiliar with the Data Loading Tools, you may find these videos helpful:
- Introducing the Data Loading Tools
- Set the Stage for Data Loading
- Source to Target Mapping for DLT
- Advanced Mapping for DLT
Step 4 Add Users to Groups
New groups were created in your ArcGIS organizations during the version 2.0 deployment. The new groups automatically get assigned a name that is different from existing groups in your ArcGIS organization. The system typically ensures the new group names are unique by adding a number to the end of the group name.
Add users to the new groups by inviting them from the group’s item page. Groups are important because they allow specific items of the solution to be shared with specific users, as well as control the permissions for those items.
Step 5 Share Version 2.0 Apps with Users
In previous versions, you may have provided apps to staff members by sharing with them the app’s URL. After deploying version 2.0, the newly deployed apps will have different URLs that need to be provided to staff members.
Step 6 Remove Previous Version
Once you have completed steps 1-5 and have confirmed the new version works and contains your data, you can optionally remove the previous version. You may also choose to keep the older version as an archive or export data from the old version to a file geodatabase. Solutions can be deleted from the My Solutions tab on the ArcGIS Solutions app by hovering over the solution card and clicking the trash bin.
To ensure you are removing the correct version of the solution, use the deployment date at the bottom of the card. The older version of the solution will have an older deployment date than the newer version. You can also click the card, which will open the solution item page, go to Settings, and confirm the version number at the bottom of the Settings page.