Latest Contributions by RobBlash

Re-test it with fonts embedded (File>Options>Save, scroll to the bottom and check the embed font option and uncheck the other 2 related options (see my screen shot). I've gotten into this habit because the report previews do not render correctly without this option checked. @Ruth_JiatengXu can you confirm Esri has tested this fix with and without embedded fonts in the report template?

Can't this be scheduled sooner? This is a big inconvenience. My company exports 100s of feature reports daily and they all include check boxes.

Already on it, thanks

Confirming I'm seeing the same behavior so this is not an isolated issue. The docx -> pdf is the workaround for now, but not ideal since it involves additional work for my team.

‎03-20-2026

I meant to put in a support ticket yesterday, but the day got away from me on other pressing issues. The FGDB export via survey123.com never completed, and exports via my retired desktop python scripts also never completed. However, my notebooks ran as expected last night. So maybe something on services9 fixed itself, or Esri found the problem via other means and resolved it. We'll see what Monday brings.

‎03-19-2026

I have a few notebooks that run nightly to backup my field data. I have 2 distinct groups of feature services, and each has a notebook for csv export and file gdb backup. So, 4 notebooks in total that have been successfully running sine November of 2025. The notebooks loop through items in an AGOL group and export them. As of early AM Monday, my 2 file gdb notebooks fail to complete (they time out while exporting a larger gdb). My first thought was a particular feature was corrupted and failing to export, but since the exports are failing on different hosted feature services, that doesn't seem plausible. So, I updated the runtimes for all notebooks to python 13 (standard), with no improvement. Has anyone else experienced similar issues? Some more background: I query only a subset of features (last 30 days) to keep the backup size manageable. So, I'm not trying to export gigantic datasets. I have some smaller datasets that succeed, but when the script hits a "larger" dataset it seems to hang. The notebooks replaced python scripts that were running nightly on a desktop for 5+ years, so I'm not in uncharted territory. These workflows work, but something has changed and impacted the success. I'm trying a manual export to file gdb from survey123.com, I will report back if/when that finishes. I will also try the old python scripts to see if they succeed.

‎03-19-2026

I like the deprecation flag as a control for the replacement items. Great idea!

‎01-27-2026

With the upcoming retirement of web app builder, we need a robust way to redirect existing web app URLs to their replacement experience builder apps. The redirect needs to happen in the app itself, and not at the item page. For a public facing web app, that just doesn't get the job done.

‎10-23-2025

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.

‎10-21-2025

I want to compare to fields in a report template but I am not having luck. I want a conditional element like this: ${if field1 != field2} some text ${/} I've tried a few ways but I can't get the syntax right. None of the below works ${if field1 != field2} ${if field1 != ${field2}} ${if field1 != '"+field2+"'} Has anyone successfully done this?

‎07-01-2025

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

‎07-01-2025

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).

‎06-30-2025

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

‎06-05-2025

@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.

‎06-03-2025

@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

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by RobBlash

Re: S123 PDF Reports with No Checkboxes

Re: S123 PDF Reports with No Checkboxes

Re: S123 PDF Reports with No Checkboxes

Re: S123 PDF Reports with No Checkboxes

Re: File gdb exports via python notebook are suddenly failing

File gdb exports via python notebook are suddenly failing

Re: Redirect Any Item to a Replacement Item

Re: Option to Redirect Applications that have been 'Retired'

Re: Compare value of 2 fields in feature report template

Compare value of 2 fields in feature report template

Re: Error generating reports when using placeholders in Report name and repeats in the template

Re: Survey123 reporting service down?

Re: Survey123 reporting service down?

Re: Attribute Transfer Tool Equivalency in ArcGIS Pro

Re: Attribute Transfer Tool Equivalency in ArcGIS Pro

Re: S123 PDF Reports with No Checkboxes

Re: S123 PDF Reports with No Checkboxes

Re: File gdb exports via python notebook are sudde...

Re: Error generating reports when using placeholde...

Re: Creating feature reports is taking a long time