Latest Contributions by Bud

@JimmyBowden  Would field highlighting help at all? If you were to highlight like-fields in the attribute table, would those fields get highlighted in the attribute pane too? Does the attribute pane in ArcGIS Pro honor AGOL/Enterprise web map > form configuration groupings? I imagine the answer is no. Edit: ArcGIS Pro Roadmap - November 2025 Support for Attribute Editing Forms - The first phase of this project will provide support in ArcGIS Pro to use attribute editing forms created in other ArcGIS applications (Map Viewer and Field Maps Designer). The second phase will provide support for building and configuring forms from ArcGIS Pro. Related Ideas:  Grey out attribute table fields Field Highlight using basic colors Provide native attribute data entry forms and form design tools ... View more

Likewise, grouping fields is possible in an AGOL web map > form configuration, for use in the editor widget in Experience Builder. I imagine the same thing can be done in Field Maps too. Editor Widget — Make read-only fields look different from editable fields Like you say, it would be nice to do this in ArcGIS Pro too.   ... View more

@JonathanMcD  The non-GIS user finds it easier to copy a feature from one layer to a different layer using the "two editor panes" setup, since both panes are always open. It would be less intuitive to navigate back and forth between two layers within the same editor pane. ... View more

@bbollin Good idea! I'll try it out. Thanks. ... View more

@AlixVezina might find this quirk/gotcha interesting:   AGOL Idea: Consistent default text field length in AGOL and Survey123 Survey123 Designer text fields are 255 characters long, but a new text field from scratch in AGOL is 256 characters long. This idea is to make the default text field length in AGOL and Survey123 consistent. One annoying thing about this quirk is that a 255-char Survey123 field gets flagged by the Feature Compare > Schema only geoprocessing tool in ArcGIS Pro as having a different length from a 256-char manually created field. That's a nuisance, because in this case, 255 vs. 256 isn't important to me. I'm copying features from a Survey123 feature layer into a manually created feature layer using the editor widget in Experience Builder.  "...the destination text field needs to be as long or longer than the source field, otherwise the attribute value will not be pasted." In this case, pasting from 255 to 256 isn't a problem; the value will get pasted without issue. It's only if it were the other way arround, 256 to 255, that would be a problem. So yeah, it's too bad that these rows are being flagged as having different field lengths, when they were meant to be exactly the same. This quirk would be a bigger problem if I were copying from 256 to 255. In that case, the copy/paste feature functionality in the Experience Builder editor widget would fail. I'd need to lengthen all the 255 fields to 256 (or shorten the 256 fields to 255), which would quite a pain: Create new fields Field calculate the values Delete old fields Fix all the broken field dependencies (somtimes using the same field name is not enough; the web map dependency still breaks)   ... View more

One annoying thing about this quirk is that a 255-char Survey123 field gets flagged by the Feature Compare > Schema only geoprocessing tool in ArcGIS Pro as having a different length from a 256-char manually created field.   That's a nuisance, because in this case, 255 vs. 256 isn't important to me. I'm copying features from a Survey123 feature layer into a manually created feature layer using the editor widget in Experience Builder.  Experience Builder questions: What are the rules when copying/pasting a feature into a different feature layer? ...the destination text field needs to be as long or longer than the source field, otherwise the attribute value will not be pasted. In this case, pasting from 255 to 256 isn't a problem; the value will get pasted without issue. It's only if it were the other way arround, 256 to 255, that would be a problem. So yeah, it's too bad that these rows are being flagged as having different field lengths, when they were meant to be exactly the same. Edit: This quirk would be a bigger problem if I were copying from 256 to 255. In that case, the copy/paste feature functionality in the Experience Builder editor widget would fail (no value pasted into that field). I'd need to lengthen all the 255 fields to 256 (or shorten the 256 fields to 255), which would quite a pain: Create new fields Field calculate the values Delete old fields Fix all the broken field dependencies (somtimes using the same field name is not enough; the web map dependency still breaks) ... View more

Thanks for looking! I submitted an idea just now: Add geometry to a feature that has no geometry. ... View more