Latest Contributions by Bud

@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

@ToddW_stl Thanks! The Survey widget was a good idea. I used a Widget Controller and put the Survey widget in it. Works well. ... View more

I checked with my I.T. department, and they said: No, I don't have any feedback on this one. This happens [with other map] locations too, not just within Survey123. If I hit enter in the Search within the Map Viewer of ArcGIS Online, the same thing occurs. The underlying Address Locator service is working fine... the Suggest and FindAddressCandidates operations both work as expected. I can send a link to my Survey123 form to Esri staff in a private message if you want to see this behaviour. ... View more