Mit der Production Mapping-Lizenz verfügbar.
Data-driven pages-enabled map documents can be imported into a product library to manage them centrally.
You can equate the following data-driven pages terms with product library terms:
| Data Driven Pages | Product Library |
|---|---|
map document | |
data frame | |
index layer | (page/features copied to the product class feature class) |
page (feature) | area of interest (AOI) |
Once imported, the product's instances and AOIs can then be searched, displayed, and selected using the Product Library tree view. To gain access to the map document, you can check out the product. Once the map document is checked out, it can be edited as a standard data-driven pages map document. Once work has been completed and it's ready to be stored again, you can check in the product. Any additions or deletions of features from the index feature class that would result in the number of and what pages there are should be done using data-driven pages tools and workflows.
If there are changes to the number of pages in the document, you are prompted to resolve these conflicts when this product is checked back in. The conflicts exist between the numbers of AOIs represented in the product library as compared to the number of pages there are now in the map document. You are presented with two options:
- Update product library with map document properties—Adds or removes the appropriate AOIs to ensure that they match the pages that are currently within the map document
- Leave conflicts unresolved—Will not update the number of AOIs in the product library to match the number of pages within the map document
The option to update the map with product library properties is not available, as you should use data-driven pages tools and workflows to manage the map document, not the product library.