Perform data search and management tasks with the ArcGIS Pro assistant (beta)
You can use the ArcGIS Pro assistant (beta) to perform data search, management, and schema design tasks. Instead of manually configuring properties or navigating multiple data design views, you can describe the information you need or the schema changes you want to make using natural language and allow the assistant to help complete the task.
With its Data Search and Management capability in ArcGIS Pro Actions mode, the assistant can help you find project and portal items, add data to maps, open property pages for database connections and dataset items, open and use data design views, and manage common geodatabase design tasks. Supported workflows include working with fields, domains, subtypes, attribute rules, contingent values, and parcel fabric records and tables.
Schema design tasks with the assistant
The assistant can help you design and modify geodatabase schemas. The assistant performs schema changes through the data design views. When you request schema changes, the assistant generates the changes as pending edits in the appropriate design view for your review.
Note:
The assistant does not save schema modifications automatically. Any schema modifications the assistant generates remain as pending edits in the corresponding design view until you save them. This allows you to review and validate the changes before applying them to the data.
Focus the conversation for schema design tasks
By default, the assistant considers all available capabilities when generating a response in ArcGIS Pro Actions mode. For more focused responses, you can optionally set the focus of your conversation to filter the capabilities the assistant considers.
Limiting the assistant to using the Data Search and Management capability ensures that, if the required data design view is not open, the assistant opens it and completes the schema design task there rather than by opening a schema-modification geoprocessing tool.
Optionally, to limit the assistant's capabilities for schema design tasks, use the assistant in ArcGIS Pro Actions mode to complete the following steps:
At the bottom of the Assistant (Beta) pane, click the assistant capabilities button
to open the Focus tab of the Assistant Settings page.Click Unselect All at the bottom of the pane.
Check the Data Search and Management box.
Check the boxes of any other capabilities needed for the conversation.
Click Back
to return to the conversation.
Make schema changes in the data design views
To make schema changes in the data design views, use the assistant in ArcGIS Pro Actions mode to complete the following steps:
Ensure you have at least one of the following items available in the current project:
A layer or stand-alone table in the active map
A dataset
A geodatabase object that supports the requested design view
In the prompt text box at the bottom of the pane, enter a request for the assistant to open one or more data design views, such as Open the Fields view and Domains view on the Buildings layer in the active map.
Press Enter or click Ask the question
to submit the request.The assistant processes the request and opens the appropriate data design views.
Enter and submit a follow-up request for the assistant to make one or more schema changes in the open views, such as Add a short integer field named AccessType with an alias of Security Access Level. Create a coded value domain named AccessType where 1 = Employee, 2 = Public, 3 = Maintenance, and 4 = Security.
The assistant processes the request and generates the requested changes as pending edits in the appropriate design views.
Review the pending edits and validate that the changes accurately fulfill the request.
Optionally, on the ribbon, on the tab for the open design view, in the Manage Edits group, click Save to apply the changes.
If the changes are not correct, in the Manage Edits group, click Discard Edits, or in the Edits group, click Delete to undo them, depending on which view you are using.
Supported data design views
The assistant supports all ArcGIS Pro data design views:
Fields view
Fields define the information stored in a dataset. You can use the assistant to create and manage fields and field properties in the fields view.
The following list identifies the field properties that you can set with the assistant:
VisibleRead OnlyField NameAliasData TypeAllow NULLHighlightDomainDefault ValuePrecisionScaleLength
The following table contains sample prompts for creating and managing fields and field properties in the fields view:
| Available functionality | Sample prompt |
|---|---|
| Add field | On the layer People, add a short integer field 'age' that uses the domain 'ValidAge' |
| Delete field | On the layer People, delete the field 'Favorite_food' |
| Alter field | On the layer People, change the alias of the field 'last_name' to 'Last Name' |
| Sort field | On the layer People, sort the fields by 'Field Name' |
| Reset field order | On the layer People, remove any sorting and filtering |
| Copy field | On the layer People, copy the 'First_name' field |
| Paste field | On the layer People, paste the field |
| Cut field | On the layer People, cut the field 'age' |
Domains view
Domains help maintain data quality by constraining the values that can be stored in a field. You can use the assistant to create and manage coded value and range domains, add or modify coded values, and update domain properties in the Domains view.
The following list identifies the domain properties that you can set with the assistant:
NameDescriptionField typeDomain typeSplit policyMerge policy
The following table contains sample prompts for creating, deleting, and managing domains and domain properties in the Domains view:
| Available functionality | Sample prompt |
|---|---|
| Add coded value domain | On the layer People, add a short integer coded value domain 'AgeClassification' with the following coded values starting at 0: 'Baby', 'Child', 'Teenager', 'Adult', and 'Senior' |
| Add range domain | On the layer People, add an integer range domain 'ValidAge' with a minimum value of 0 and a maximum value of 164 |
| Delete domain | On the layer People, delete the domain 'ValidAge' |
| Alter domain | On the layer People, add the coded value pair (7, Toddler) to 'AgeClassification' |
Subtypes view
Subtypes are a subset of features in a feature class, or objects in a table, that share the same attributes. Subtypes are used as a method for categorizing data. You can use the assistant to create and configure subtypes, assign subtype fields, set default subtype values, and apply coded or range domains to the fields of a subtype in the Subtypes view.
The following list identifies the subtype properties that you can set with the assistant:
CodeName
The following table contains sample prompts for creating, deleting, and managing subtypes and subtype properties in the Subtypes view:
| Available functionality | Sample prompt |
|---|---|
| Set subtype field | On the layer People, set the subtype field to 'age_group' |
| Set default subtype | On the layer People, set the default subtype to 'Adult' |
| Add subtype | On the layer People, add the subtype '(3, Adult)' |
| Delete subtype | On the layer People, delete the subtype with Code 3 |
| Alter subtype-level domain | On the layer People, set the subtype-level domain of the field 'Age' for subtype 'Adult' to 'ValidAdultAge' |
| Alter subtype-level default value | On the layer People, set the subtype-level default value of the field 'Age' for subtype 'Adult' to 1 |
Contingent Values view
Contingent values make values in one field dependent on values in another related field. They are created for groups of fields in a table or feature class. Contingent values help improve data quality by guiding editors toward valid field combinations and reducing data entry errors. You can use the assistant to create, delete, and manage field groups and contingent values in the Contingent Values view.
The following list identifies the field group properties that you can set with the assistant:
NameField namesIs editing restrictive
The following list identifies contingent value properties that you can set with the assistant:
Field group nameSubtype nameField valuesID(only forDeleteandAlter)
The following table contains sample prompts for creating, deleting, and managing contingent values and field group properties in the Contingent Values view:
| Available functionality | Sample prompt |
|---|---|
| Add field group | On the layer People, add the field group 'OccupationFieldGroup' consisting of the fields 'occupation' and 'sub-occupation' |
| Delete field group | On the layer People, delete the field group OccupationFieldGroup' |
| Alter field group | On the layer People, add the field 'is_government_job' to the field group 'OccupationFieldGroup' |
| Add contingent value | On the layer People, add a contingent value to the field group 'OccupationFieldGroup' where if the occupation is Engineering, then the sub-occupation must be 'Software', 'Electrical', or 'Mechanical' |
| Delete contingent value | On the layer People, delete the contingent value with the ID 3 and associated with the field group 'OccupationFieldGroup' |
| Alter contingent value | On the layer People, change the contingent value with ID 3 to include any sub-occupation when the occupation is 'Undefined' |
Attribute Rules view
Attribute rules enhance the editing experience and improve data integrity for geodatabase datasets. They are user-defined rules that can be used to automatically populate attributes, restrict invalid edits during edit operations, and perform quality assurance checks on existing features.
You can describe the behavior you want to enforce, and the assistant generates the corresponding rule definition in the Attribute Rules view. When appropriate, the assistant can generate Arcade expressions based on the requested behavior using the Arcade assistant. This workflow allows you to focus on the intended data behavior rather than manually authoring Arcade expressions.
The following list identifies the attribute rule properties that you can set with the assistant:
NameDescriptionRule type(Calculation,Constraint,Validation)TagsSubtype infoExpressionIs disabledError numberError messageCalculation rule properties:
Field nameIs attribute value editableHas insert triggerHas update triggerHas delete triggerTriggering field namesIs batchExclude from application evaluation
Constraint rule properties:
Has insert triggerHas update triggerHas delete triggerTriggering field namesExclude from application evaluation
Validation rule properties:
Severity
The following table contains sample prompts for creating and managing attribute rules and attribute rule properties in the Attribute Rules view:
| Available functionality | Sample prompt |
|---|---|
| Add calculation rule | On the layer People, create a batch calculation rule 'TotalPetsRule' that stores the sum of 'TotalDogs' and 'TotalCats' to the uneditable field 'TotalPets' |
| Add constraint rule | On the layer People, create a constraint rule 'AgeRule' where 'Age' must never be less than 'TotalAgeWorking' on every update and insert |
| Add validation rule | On the layer People, create a validation rule 'AgeRule' where 'Age' must never be less than 'TotalAgeWorking' and reports the error number 501, error message 'Invalid age', and with severity 5 |
| Delete attribute rule | On the layer People, delete the attribute rule 'ValidDrivingAgeRule' |
| Alter attribute rule | On the layer People, change the attribute rule 'TotalPetsRule' to be an immediate calculation rule and to trigger on every insert and update |
Tips for successful schema design tasks
To help the assistant generate schema changes that more closely match your intended design, follow these tips:
Identify the target layer, table, or dataset whenever possible.
Describe the outcome you want rather than individual interface steps.
Review proposed schema changes before saving them.
Break complex requests into smaller tasks when appropriate.
Review and verify generated Arcade expressions and attribute rules before applying them to production data.