There are a number of things to be aware of when packaging published maps, ranging from data conversion incompatibilities to unsupported functionality in the map. It is important to keep in mind that all the parts of one data type may not be interchangeable with the parts of another data type. The loss or modification of some cartographic functionality may occur.
These types of limitations do not cause error messages or warnings.
Be aware of the following limitations that do not cause packaging errors but may cause unexpected symbol rendering in the map. If a layer is symbolized on a field that is modified, the layer symbology will display with default symbols. The following situations may cause the field name to change.
It may be best to use the copy option for compressed image formats. The ERDAS IMAGINE format, available with data packaging, is uncompressed and file sizes could be quite large. Raster data file size and memory usage should always be of concern.Packaging raster layers with the clip setting
Colors can shift when rasters are clipped. Some renderers stretch colors across the minimum and maximum values of the raster. Clipping the raster could change the minimum and maximum values and cause all the colors to shift.
If you are using hyperlinks that reference files, the files will have to be copied into the data package manually. The hyperlinks will also need to be updated to reflect the file location in the data package. You could also create hyperlink paths prior to publishing that are specific to the data package you plan on creating.
If your hyperlink attribute contains the filename, you can place the file in the same directory with the published map. If no path is present the ArcReader Identify and Hyperlink tools will look for the hyperlink file in the published map's folder.
Packaging inserted picture elements
Computer-aided design (CAD) layers are always copied into the data package, and they will not be converted to the chosen format.Packaging layers with ArcMap joins and relates
Joins and relates are created for layers in ArcMap by right-clicking a layer in the ArcMap table of contents, pointing at Joins and Relates, and clicking Join or Relate. The information for the join or relate is stored in the map and in the published map when it is created. When you package the published map, joins and relates are not maintained in the data package.
Packaging layers with relationship classes
Published maps with relationship classes can be packaged with the copy setting. If the Intersect or Include All setting is used, the relationship class will not be packaged.Packaging layers with definition queries
Packaging published maps that contain layers with a definition query is not recommended. A definition queries where clause may not be valid for the chosen data package format. A query that works for a shapefile will not work for a geodatabase.
A shapefile query:
"NAME" = 'California'
A personal geodatabase query:
[NAME] = 'California'
The field name declaration is not interchangeable. If a shapefile layer with a definition query is packaged to a geodatabase, the resulting published map will not display any features, as the definition query will not return any features.
Creating data packages for published maps that contain selection layers may alter the result of the selection layer.
Selection layers persist themselves by using the features object ID. When you create a data package, there is no guarantee that the data packaged feature's object ID will match the source feature's object ID. This is particularly true if the data package only includes features that intersect the data frame.