Not all data sources are supported by web layers, web maps, and web scenes. A layer in your map or scene uses an unsupported data source. The <value> parameter identifies the layer.
Use one of the following solutions:
- Replace the unsupported data source with a supported database feature class.
- Do nothing. The unsupported layer will be excluded from the web layer, web map, or web scene.
Unsupported layer types usually fall into one of the following categories:
- Service layers—Although this warning can occur with any service layer, it most commonly occurs with a basemap layer when you share the contents of a map as a web layer. In this case, do nothing; the basemap layer will be excluded, and all other layers will be shared.
- TIN layers—TIN layers are not supported as elevation surfaces in web scenes.
- CAD layers—To share CAD layers, the source data must be converted to feature classes. For more information, see CAD data in ArcGIS Pro.
- Revit layers—Revit layers are only supported for sharing as a web scene layer to ArcGIS Online or ArcGIS Enterprise 10.7 or later.
- Tile packages and vector tile packages—These packages cannot be shared as part of a web layer, web map, or web scene. Replace the package with the source data used to create the package.
- Scene layer packages—All scene layer packages can be shared as part of a web scene to ArcGIS Online. Support for sharing to ArcGIS Enterprise depends on the version.
- Integrated mesh, multipatch, and point scene layer packages are supported for sharing to ArcGIS Enterprise 10.5 or later.
- Point cloud scene layer packages are supported for sharing to ArcGIS Enterprise 10.5.1 or later.
- Building scene layer packages are supported for sharing to ArcGIS Enterprise 10.7 or later.
- SQLite data—Data in an SQLite database must be converted to a file or enterprise geodatabase feature class before sharing.
- Voxel layers—Voxel layers are not supported in a web scene.
It's not practical to provide a complete list of supported data sources because the list is long and must be qualified depending on the output web layer type and on your portal or server configuration. A general guideline is to convert unsupported data sources to feature classes using tools in the Conversion toolbox.