Creating a field configuration table using a new 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 the 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 do not already have a product library, the Field Configuration Manager can be used to walk you through the process of creating a new product library. First, you will need to ensure that you have a database that can be used as the product library. When prompted, you will point to this database, and new tables, like the field configuration table, will be added for storing information about your data. You will also 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. This allows you to be able to set up the configurations for the entire database even if you only have a subset of the feature classes loaded in your map. Once the necessary information has been collected, you can begin configuring how the fields will behave.

Schritte:
  1. Start ArcMap.
    TippTipp:

    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.

  2. If necessary, load data in the map.
  3. On the main menu, click Customize > Toolbars > Production Editing.
  4. On the Production Editing toolbar, click Production Editing > Field Configuration Manager.

    The Set Product Library dialog box appears.

    If a product library has already been specified, the Update Workspace message appears. Proceed to step 7.

    Set Product Library dialog box
  5. Click Browse.

    The Choose Product Library Location dialog box appears.

  6. Navigate to the geodatabase that is going to be used as the product library.
  7. Click Open.

    The Update Workspace message appears.

  8. Click Yes to update the geodatabase.

    The geodatabase is updated to a product library, and an Update Workspace message appears to update the workspace for the data to a production database.

  9. Click Yes to update the data workspace.

    The production database tables are copied to the current workspace, and a new data model is created based on the feature classes in the geodatabase.

    The Set Product Library dialog box appears.

  10. Click OK.

    The Field Configuration dialog box appears.

    Field Configuration dialog box before field configuration table is created

  11. Click Create Configuration.

    The Creating Field Configurations window appears with a progress bar. Once the processing is complete, the Field Configuration dialog box appears.

    Field Configuration dialog box without tables

  12. 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.

    Choose Product Class Tables to Edit dialog box

  13. 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 respectively display or hide all the subtypes within the feature classes.

  14. Click OK.

    The Field Configuration dialog box appears with the selected feature classes and tables in the Current Fields Configuration Table list.

    Field Configuration dialog box with tables and feature classes

  15. 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.


9/30/2010