Latest Contributions by RobBlash

Fields are not in a repeat. The site would accept the syntax for ${if field1 != field2} (no errors) but it didn’t actually produce the expected result when exporting a sample report. I think the other 2 options threw a syntax error when trying to upload the template.  Thanks for the reply, in the end I updated the survey to eliminate the duplicate values and put a static “NA” in field 2 that I can easily query for in the report template.  ... View more

BUG-000177504 was fixed lats night FYI, I'm seeing the expected behavior using fields for naming with repeats containing images. ... View more

The bug isn't showing up in the support search, but it was specifically for the scenario I mentioned above.  The bug was fixed last night, give it another shot. I'd open a support ticket otherwise, since there could have been multiple issues (we're seeing something with domains too in reports).   ... View more

It's a know bug. The issue is using fields in your report name, and your survey contains a repeat with an image question. BUG-000177504 ... View more

@Scott_Harris I’m aware of the option to clear the field mappings, but this posss 3 problems: In a project that had many layers, there will be many combinations of source and target fields to clear. this is not time efficient.  This also requires users to take extra steps to disable many possible outcomes that are unwanted, versus requiring a user to configure the specific outcome that they do want.  And finally, if I’m understanding the field mapping correctly, clearing all existing field mappings will cause subsequent copy paste operations to exclude attributes.  ... View more

@JenniferCadkin thanks for the additional insight on the tool. I strongly believe that automatically filling the field mapping matrix with all column/layer combinations across a project is a huge source of the trouble that folks are having with the attribute transfer tool. Put bluntly, this is wildly different than the behavior in ArcMap, and seems to cause a lot of frustration from seasoned users. I also do not think this makes Pro any easier for novice users, because they are likely unaware of the potential pitfalls this introduces. Either way, there’s massive risk for data corruption for seasoned and novice users alike when everything is “on” by default for attribute transfers.  I’ll use this as a shameless opportunity to plug my idea for a separate field mapping for attribute transfers https://community.esri.com/t5/arcgis-pro-ideas/create-a-separate-field-mapping-for-the-attribute/idi-p/1617440/jump-to/first-unread-message Thinking through it further, it may make more sense to confine field mapping to the attribute transfer tool alone (like it was in Arc Map) and only enable those mappings that are specifically turned on by the users. I also struggle to see the use case for field mapping in any other tools. For a copy/paste operation it’s intuitive for any common fields between the source and target to come across. IMO that’s expected in a “copy”. For any data moving operations where you only want to carry across specific fields, or you want source.A column to populate target.B column, the append tool has pretty powerful field mapping capabilities to handle the process. In short, I think the project-wide field mapping in Pro is trying to solve a problem that does not exist, with the added expense of introducing a whole host of other problems for tools such as attribute transfers    ... View more

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

@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

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

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

@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

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