Working with incomplete derived data
ModelBuilder is engineered with intelligence to know how tools will change data before the tool is executed. This behavior is necessary to be able to continue building a workflow after including some tool that alters data. The best illustration of this behavior involves using the Add Field and Calculate Field tools, as illustrated below. If a new field is added using the Add Field tool, the output variable of the Add Field tool will be updated to contain the new field. When the Calculate Field tool is opened, it will see the new field, even though the Add Field tool has not yet been executed. This is necessary to allow the other parameters of the Calculate Field tool to be specified, and the model workflow continued without first executing the Add Field tool.
While ModelBuilder has the ability to read what changes most tools will make to data before the tool is executed, there are some tools where ModelBuilder cannot see the derived data or values the tool will create. In these cases, the derived output data cannot be updated to include those changes before execution. Such data is considered incomplete derived data.
Using incomplete derived data
When some process creates incomplete derived data, but it is necessary to use this derived data as input to another process, there are two possible options to work around this limitation:
- Type in a value—If the specific changes missing in the incomplete derived data are known, values can be manually entered into a parameter in the tool dialog box.
- Run a process—In ModelBuilder, the process that creates incomplete derived data can be run individually. After the process has been executed, the derived data will complete.
Type in a value
The Create Table tool adds the field Field1 to the new table, but this new field will not appear in the list of fields that can be deleted using the Delete Field tool; the Create Table tool creates incomplete derived data. Ultimately, Field1 must be deleted from the table, but it is not included in the automatically generated list of fields that can be deleted from the table.
Since Field1 is known to exist in the table after the Create Table tool is executed, add Field1 manually to the list of fields to be deleted using the Add Field button in the Delete Field tool dialog box.
After adding Field1 to the list of fields to delete, a warning will be raised that Field1 does not exist. This warning can be ignored, since by the time the Delete Field tool is executed, Field1 will exist.
Run a process
- In ModelBuilder, you can run individual processes by selecting the tool, right-clicking, and clicking Run.
Some tools that create incomplete derived data
The Import From Interchange File tool reads an ArcInfo interchange file (.e00 file) containing ArcInfo coverage data. This tool cannot determine any of the output dataset field names, their attributes, or the geometry type until the tool is executed. Many of the other tools in the Conversion toolbox will also create incomplete derived data.
All script tools will output incomplete derived data, unless the script tool has been programmed with a Tool Validator class to update the definition of the derived data variable. To learn more, see Customizing script tool behavior.
The Split tool, which creates new feature classes in a workspace, does not know the number or names of feature classes that will be created until the tool executes; this is considered incomplete derived data.
The Create Table tool, which automatically adds certain fields depending on the type of table output (geodatabase, .dbf, or INFO), does not know the names of the fields the tool will add until the tool executes; this is considered incomplete derived data.