AllSource is a professional desktop application designed for the geospatial professional. ArcGIS AllSource is an intelligence workstation designed for the intelligence professional. When you're ready to migrate from AllSource 2.x to ArcGIS AllSource, use the information below as a guide.
Projects
- Projects and project templates (.aprx, .ppkx, and .aptx files) saved in AllSource 2.x and ArcGIS Pro 3.0 can be opened and converted for use in ArcGIS AllSource. However, projects and project templates saved in ArcGIS AllSource cannot be opened in AllSource2.x or ArcGIS Pro 3.0.
- You cannot save a copy of an ArcGIS AllSource project (.asrx file) that can be opened in AllSource 2.x.
- User configuration settings are carried over from AllSource projects.
- Link charts, and their associated maps, created in AllSource 2.9, AllSource 3.0, ArcGIS Pro Intelligence 2.9, and ArcGIS Pro Intelligence 3.0 work in ArcGIS AllSource.
- Timelines, with their associated maps, created in ArcGIS Pro Intelligence 2.9 and 3.0 work in ArcGIS AllSource.
Documents
- Map, layer, report, and layout files (.mapx, .lyrx, .rptx, and .pagx) cannot be opened in AllSource 2.x once they are created or saved in ArcGIS AllSource.
- Globe service layers are not supported. It is recommended that you republish the original layer to a supported service, such as map service or feature service. For projects using a globe service for elevation, the default Esri Terrain 3D service can be used.
Packaging
- Geoprocessing tools for packaging create packages that allow you to collaborate with other team members using ArcGIS Pro 3.0 and earlier.
- Packages you create using the commands on the Disseminate ribbon—such as layers, map packages, and project packages—can be used in AllSource 2.x and AllSource 3.0.
Sharing
- Web layers and services are shared with content that is compatible with the target server. ArcGIS AllSource supports ArcGIS Enterprise 11.1 and later.
- When creating a service definition that contains server connection information, the .sd file contains content that matches the server version.
- When creating a connection-neutral offline service definition file, you must specify the target server version (ArcGIS Enterprise 11.1 or later, or ArcGIS Online) to ensure that the file contains content compatible with your server version.
- Mobile map packages can be opened in ArcGIS AllSource and AllSource 2.x and 3.0.
Geoprocessing
- Custom ArcGIS toolbox files (.atbx) are created by default in AllSource 3.0 and are compatible with AllSource 2.9.
- Custom legacy toolbox files (.tbx) are read-only in ArcGIS AllSource. Existing .tbx files and their tools are read-only in ArcGIS AllSource but continue to work without required changes. To make changes to a tool, you must copy the tool to an .atbx file.
- You can package toolboxes in ArcGIS AllSource to maintain compatibility with AllSource 2.x.
- You can upgrade tools and toolboxes from AllSource 2.x by copying them to an .atbx file.
Python
- In ArcGIS AllSource, use the openpyxl or pandas library to work with .xlsx files. The xlrd library version 2.0.1 does not support reading or writing of Microsoft Excel files (.xlsx).
- The Describe property workspaceFactoryProgID returns a value of esriDataSourcesGDB.MemoryWorkspaceFactory for a memory workspace. In AllSource 2.x, it returns a value of esriDataSourcesGDB.ColumnaDBWorkspaceFactory.
- Scripts created in AllSource 2.9 and AllSource 3.0 work in ArcGIS AllSource 1.0.
- Scripts written in AllSource 2.x that use the arcpy.mp module work in ArcGIS AllSource; however, the CIM version must be updated to access the version 3.0 CIM. For more information, see Python CIM access.
General recommendations
To assist with the migration process, the following are recommended:
- Create backups or project packages when you are collaborating with other organizations or team members who are using AllSource, as they must be converted before you use them in ArcGIS AllSource 1.0.
- When sharing, use ArcGIS AllSource with ArcGIS Enterprise or ArcGIS Server 11.1.