When input tables are from a file geodatabase, tables generally join in the order listed in the Input Tables parameter. The Add Field button allows you to add expected field(s) so you can complete the Make Query Table dialog box and continue to build your model. In ModelBuilder, where the preceding tool has not been run, or its derived data does not exist, the Fields and Key Fields parameters may not be populated with field names. The Fields and Key Fields parameters' Add Field button is used only in ModelBuilder. If you add more than one geometry column, the tool will display an error when you click OK and execution will stop.įor details on the syntax for the Expression parameter, see Building an SQL Expression or SQL Reference. If an SQL expression is used but returns no matching records, the output feature class will be empty.įeature classes can be joined, but the fields list must contain at most one field of type geometry. The key fields list lets you choose several columns if the combination of these columns is needed to define unique values. Without an ObjectID column, selections will not be supported. This information defines how rows are uniquely identified and is used to add a dynamically generated ObjectID column to the data. The tool allows you to provide a key field option and key fields list. The order of the fields in the field list indicates the order the fields will appear in the output layer or table view. If the output result is a layer, it may be persisted to a layer file using the Save To Layer File tool or to a feature class using the Copy Features tool.
If a Shape column is added to the field list, the result is a layer otherwise, it is a table view. The layer that is created by the tool is temporary and will not persist after the session ends unless the document is saved.Īll input feature classes or tables must be from the same input workspace.
0 kommentar(er)
