Title Export Reporting Data
- For optimal read performance, a database connection is recommended.
- For optimal write performance, a mobile geodatabase (sqlite) is recommended for the Output Geodatabase.
- File geodatabases only support a subset of views.
- If you specify the utility network controller dataset, association and controller views will only be created to the input datasets if the target dataset name matches the class name in the source utility network.
- You can target the same target dataset with multiple Input Datasets. This allows you to specify the layers with definition queries or subtype group layers for the Input Datasets and load their records to a single target dataset.
- If the length of the view name exceeds the table name limit, the subtype description will be replaced with its code.
ExportReportingData (output_gdb, {datasets}, {output_options}, {controller_dataset}, {field_override}, result)
| Parameter | Explanation | Data Type |
|---|---|---|
| output_gdb |
Dialog Reference
<p>The output geodatabase where the records will be exported.</p> |
DEWorkspace |
| datasets (Optional) |
Dialog Reference
<p> The datasets to export. <ul><li>Dataset - the dataset to export. Using a layer in a map can improve performance of the execution of the tool and the validation of geoprocessing while populating the tools parameters. If a layer is specified, only the selected records and the layer's visible fields will be exported.</li><li>Table Name - the name of the table in the Output Geodatabase. If it doesn't exist, it will be created.</li><li>Include Geometry - For feature classes, this will export the geometry column.</li></ul> </p> |
GPValueTable |
| output_options (Optional) |
Dialog Reference
<p>Various options that control how the output is created. Create Database Views is only available with an ArcGIS Pro Standard or Advanced license. <ul><li>Load Records - Load the records into target table.</li><li>Create Database Views - Creates common database views on the exported tables. If the length of the view name exceeds the table name limit, the subtype description will be replaced with its code.</li><li>Truncate Tables - Truncates tables in the Output Geodatabase before loading records.</li><li>Load Associations - When exporting a Utility Network, load the association records.</li><li>Load Subnetwork Controllers - When exporting a Utility Network, load the subnetwork controller records.</li></ul> </p> |
GPMultiValue |
| controller_dataset (Optional) |
Dialog Reference
<p>The Utility Network. When specified, additional options will be available.</p> |
GPUtilityNetworkLayer |
| field_override (Optional) |
Dialog Reference
<p> A table defining field names and visibility for the subtype views. This parameter is only applicable when "Create Database Views" is checked. The Map Layers to CSV tool in the Map toolset can be used to generate a table in this format from a map. It has the following schema: <ul><li>Dataset - The name of the target table in the output geodatabase.</li><li>SubtypeCode - The subtype code used in the view definition.</li><li>FieldName - The name of the field in the dataset.</li><li>ViewFieldName - The name of the field as it appears in the view.</li><li>Visible - If the field will be included in view.</li></ul> </p> |
GPTableView |
| DEWorkspace |
workspace