Creating a field configuration table using an existing product library
Using Production Mapping, you can define and manage the visibility and behavior of attributes through the field configuration table. Production Mapping tools such as Feature Manager and Production Dissolve take advantage of the field configuration table. The product library is used as the central location for storing the field configuration table.
If you already have a product library, the Field Configuration Manager can be used to choose the product library and the schema (or data model version) of the database whose fields you want to configure. If you have already stored the schema of your data as a data model version and product class version, you will be prompted to select these. Otherwise, you will need to ensure that you have loaded at least some of the feature classes from the production database you want to configure. As part of this process, the entire schema of your production database is extracted as a data model version. Once the necessary information has been collected, you can begin configuring how the fields will behave.
If you have already selected any of these properties, such as the product library or data model version, using the Production Mapping properties, you will not be prompted for this information from the Field Configuration Manager.
- Start ArcMap.Sugerencia:
If the ArcMap - Getting Started dialog box appears, you can open a new or existing map document. You can also check the Do not show this dialog box in the future check box and click Open.
- If necessary, load data in the map.
- On the main menu, click Customize > Toolbars > Production Editing.
-
On the Production Editing toolbar, click Production Editing > Field Configuration Manager.
The Set Product Library dialog box appears.
-
Click Browse.
The Choose Product Library Location dialog box appears.
- Navigate to the geodatabase that is going to be used as the product library.
-
Click Open.
The Update Workspace message appears.
-
Click Yes to update the geodatabase.
The geodatabase is updated to a product library, and an Update Workspace message appears that asks you to update the workspace for the data to a production database.
-
Click Yes to update the data workspace to a product library.
The Choose Model Versions dialog box appears if there are several data model versions in the product library.
If there is only one data model, the Data Model Version dialog box appears. You can proceed to step 12.
- Check the check boxes next to the model versions supported by the production database.
-
Click OK.
If you check more than one data model, the Set Current Data Model Version dialog box appears. If you only choose one data model version, the Data Model Version dialog box appears.
- Click the Choose Current Data Model Version drop-down arrow and choose the current data model version for the production database.
-
Click OK.
The Setting Data Model Version window appears with a progress bar.
The Data Model Version dialog box appears.
- Choose a data model option.
-
Click OK.
The Field Configuration dialog box appears.
-
Click Create Configuration.
The Creating Field Configurations window appears with a progress bar. Once the processing is complete, the Field Configuration dialog box appears.
-
Click Tables to Edit.
The Choose Product Class Tables to Edit dialog box appears with a list of feature classes and tables in the data model.
-
Check the check boxes next to the feature classes and tables in the Choose Table(s) to Edit list whose filters you want to edit.
You can right-click in the list and click Select All or Clear All to check or uncheck all the check boxes, respectively. You can also right-click in the list and choose Expand All or Collapse All to display or hide all the subtypes within the feature classes.
-
Click OK.
The Field Configuration dialog box appears with the selected feature classes and tables in the Current Fields Configuration Table list.
To edit fields individually, proceed to Editing attributes in a single feature class. To edit fields in multiple feature classes and tables, proceed to Editing attributes across multiple feature classes.