|
IDEA
|
Thanks @Scott_Harris, that's not quite what I'm after, but it's close. I've started a new idea. If you see fit to merge them that's fine with me. I think this would be very complimentary to the attribute transfer enhancements at 3.5, and would be another big step in the right direction to make ArcGIS Pro easier to use for the folks who spent years using ArcMap. Create a separate Field Mapping for the attribute ... - Esri Community
... View more
05-22-2025
04:47 AM
|
0
|
0
|
1888
|
|
IDEA
|
The attribute transfer tool relies on the field mapping dialogue in Edit>Settings. This field mapping is also shared across all editing operations across ArcGIS Pro. This causes several problems: A common field mapping introduces data integrity issues when using the attribute transfer tool, because the field mapping is automatically pre-populated across all layers within the map. For effective use of the attribute transfer tool, the field mapping needs to be set at a granular level on an as-needed basis for the workflow at hand, as it was in ArcMap. Without this, there is a great risk of unintentionally introducing error into your datasets by using the attribute transfer tool. Updating the field mapping for an attribute transfer workflow results in changes to the attributes populated in a Copy/paste operation. Copy/paste typically serves a very different purposes than attribute transfers in my workflows. I almost always want all matching fields to come across in a copy/paste, whereas I typically want specific fields only to come across using attribute transfer. Having a separate attribute transfer field mapping will result in more effective use of this tool. In it's current iteration, the attribute transfer tool takes significantly more time and effort to us in ArcGIS Pro vs. ArcMap.
... View more
05-22-2025
04:45 AM
|
9
|
3
|
2004
|
|
IDEA
|
@Scott_Harris are there any plans to separate the attribute mapping for the attribute transfer tool from the “global” attribute mapping that exists across an ArcGIS Pro project? This tends to cause issues, especially because it is pre-populated with all fields in all layers in the project. Copy/paste operations typically serve very different purposes than attribute transfers in my workflows. I almost always want all matching fields to come across in a copy/paste, whereas I typically want specific fields only to come across using attribute transfer.
... View more
05-21-2025
03:30 PM
|
0
|
0
|
1947
|
|
POST
|
Are you still having issues? I have nightly scripts that run on some AGOL feature services, and they failed with the same 400 error "Unable to perform query. Please check your parameters." Whatever the issue was seemed to have fixed itself, because after much wasted time trying to troubleshoot the problem, the scripts suddenly started working again.
... View more
11-06-2024
11:07 AM
|
0
|
0
|
1133
|
|
IDEA
|
Adding to this, two more things needed for equivalency: A dedicated field mapping setting for the attribute transfer tool (apparently the current field mapping also impact copy/paste attributes) Trace network (or map topology) connectivity being maintained when transferring geometry.
... View more
06-20-2024
12:20 PM
|
0
|
0
|
4081
|
|
IDEA
|
@Scott_Harris The attribute transfer tool needs it's own dedicated field mappings. Attribute transfer and copy/paste attributes have two very different use cases. Having them intertwined via a shared field mapping setting has the huge potential for unintended data corruption, I've seen a few examples in the community and my organization. IMO this does not meet the same level of functionality that was present in ArcMap for years.
... View more
06-20-2024
12:19 PM
|
0
|
0
|
2211
|
|
IDEA
|
When filtering a feature service using a field that has a domain, the only filtering option is to choose from the domain list. It would be very helpful to have other filter options, particularly "contains the text" or "starts with". My domain looks like this: C_2021 C_2022 C_2023 and so on. I would like to filter MyField like 'C_%' so any newly added domain values are automatically picked up without updating the view. For now, I have to filter like MyField = 'C_2021' OR MyField = 'C_2022' OR MyField = 'C_2023'
... View more
04-12-2024
09:00 AM
|
4
|
1
|
966
|
|
POST
|
I've tested on an iPad this morning and the issue appears to be fixed. I am assuming it's working as expected on iPhone too, but I'm waiting on an iPhone user to come online so I can bug them to test it.
... View more
03-18-2024
04:36 AM
|
1
|
0
|
1391
|
|
POST
|
Esri indicated to me in an email that the downloads from the website will not be updated until Tuesday, but I am seeing the updates in Google Play store and iOS App Store.
... View more
03-18-2024
04:34 AM
|
1
|
0
|
3979
|
|
POST
|
Awesome, thanks for the update. I just tested on Android (Pixel 7 pro) and it seems to be resolved. I will test on iOS tomorrow.
... View more
03-17-2024
01:13 PM
|
0
|
0
|
3991
|
|
POST
|
100% agree with this statement. I'm glad to see all of the progress that has been made with Survey123 in the last few years, and I know that the increased complexity makes bugs more likely. However, the impact of these bugs is also increased since we've increased adoption across many of our field workflows. When folks in the field have been burned by a bug its pretty hard to regain their trust. This is especially true for the folks that resist the shift to a non-paper solution in the first place. I suppose this is a lesson learned that we need to pay more attention to the betas, but the struggle to find extra time for this is real. I hope Esri will also step up to increase their internal testing.
... View more
03-10-2024
05:21 AM
|
2
|
0
|
4121
|
|
POST
|
@ChristopherCounsell wrote: If anyone reading this issue is impacted by the bug, please contact technical support so your organization is attached to the bag. Just put in a request saying please attach us to BUG 00016581. If it's impacting you majorly like it is me, please also consider escalating the defect via My Esri: https://support.esri.com/en-us/knowledge-base/escalate-a-bug-000024129# This is great advice, the more impact visible to Esri the greater the likelihood that it is fixed quickly. I always try to frame it as number of surveys impacted and number of users impacted to help drive the point home about how disruptive the bug is. I'm also working with some other Esri contacts to hopefully expedite a fix.
... View more
03-04-2024
02:11 PM
|
2
|
0
|
5987
|
|
POST
|
Support just told me that they have logged a new bug for this issue, BUG-000165581- Survey123 form jumps or scroll to the image or signature questions. I am unable to locate the bug details when searching support, but I will update this when I get more info.
... View more
03-04-2024
06:01 AM
|
3
|
2
|
6031
|
|
POST
|
I am having the same issue with all of my many surveys. I currently have a support ticket open with Esri (03567308). The initial response was to assign an old 2016 bug to the problem, however this is a new problem because the issue didn't show up until last weeks v3.19.120 update. On Friday I pushed back on support to review this further and I am awaiting an update. As mentioned above, the form unexpectedly jumps back to a photo once a photo has been attached and there is further interaction with the form. Edit: See attached video showing the same behavior that @WetherbeeDorshow has shown in their video.
... View more
03-04-2024
04:51 AM
|
3
|
0
|
6046
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 3 | 2 weeks ago | |
| 1 | 03-20-2026 04:14 AM | |
| 1 | 07-01-2025 05:11 AM | |
| 1 | 06-13-2022 11:18 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|