If you select a feature from a layer that doesn't have a custom configuration, the Attribute Form still works - it just displays all fields in a default way:
•All fields are placed in one group called "generated fields"
•Fields appear in no particular order
•Each field shows with its title and an appropriate input control based on its data type
It's similar to opening a spreadsheet where all columns are visible with no grouping or custom layout. It works, but it's not optimized for your specific workflow.
Automatic Field Information
For any field you don't explicitly configure, the Attribute Form automatically retrieves metadata from the feature source (your database or feature service). This includes:
Property |
Description |
Example |
|---|---|---|
AliasName |
Used as the display label for the field |
"Installation Date" instead of "INST_DT" |
Field Type |
Determines the input control |
Text box for strings, date picker for dates, checkbox for booleans |
Length |
Sets character limits for text fields |
Name field limited to 50 characters |
Nullable / Required |
Determines if the field must have a value before saving |
Required fields marked with asterisk (*) |
Domains |
Provides dropdown lists or ranges with valid values |
Code-Value: PVC, Steel, Copper; Range: 0-200 PSI |
Readonly |
Disables editing for system-managed fields |
ObjectID, creation date, calculated geometry |
Example:
A "PipeLength" field with type "Double", not nullable, and a range domain of 0-1000 feet would automatically appear as a required number input that only accepts values between 0 and 1000.
