Latest Contributions by RobBlash

‎10-26-2022

After some work attempts it seems like any numeric character in the filtering will throw the error. I have a premium support ticket in already, will report back.

‎10-26-2022

I'm getting an error when filtering on integer fields this morning. This was working fine prior to the update yesterday. Anyone else? I'm going to submit a support ticket but also posting here to see who else is having trouble.

‎08-16-2022

Thanks Brianna. You were correct it was my settings, somehow this got turned off despite always being on in the past.

‎08-12-2022

The native spell checking in text boxes in Chrome does not work here, why is this suppressed?

‎08-12-2022

I've had many user complaints since the Close Survey menun was re-ordered in the field app. IMO this was poorly executed, and solving a problem that doesn't really exist). The update should have been to add a confirmation warning when tapping "Close and lose hcanges". Please see my Idea to revert: https://community.esri.com/t5/arcgis-survey123-ideas/restore-the-original-quot-close-survey-quot-menu/idi-p/1202364 Background on the update if you are not familiar: https://community.esri.com/t5/arcgis-survey123-blog/what-s-new-in-arcgis-survey123-july-2022/ba-p/1197191

‎08-12-2022

A change in the last update (July 2022) has re-ordered the "Close Survey" menu in the field app. While this may have been well intentioned to help new users, it was poorly executed and negatively impacts a large pool of existing users. Seasoned users will have to re-learn their muscle memory ont jis menu, and new users will still have to learn the menu layout regardless of where the choices are. So the only real effect of this change was to cause many seasoned users to accidentally deleted drafts instead of save them. PLEASE REVERT THE MENU, AND ADD A PROMPT TO CONFIRM CLOSE AND LOSE CHANGES. This is what the update should have been from the start!! -OR an alternative update: Replace the upper-left X with 2 buttons: a trash can (with warning) to close and delete, and a save button to close and save draft. Screen shot from the blog, with my markup: https://community.esri.com/t5/arcgis-survey123-blog/what-s-new-in-arcgis-survey123-july-2022/ba-p/1197191

‎08-10-2022

Thanks, I was able to work with support to get a bug logged on the GS22 Ultra issue: https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDE0OTk2Mg== @DerrickWestoby I agree with your first approach, when something fails I generally try again an hour later On this specific issue my org has a known user with a known device (Samsung GS22) that causes intermittend issues documented with a bug. So, I just deal with the several surveys a week that come through with the problem. @DougBrowning try extracting the full EXIF data from the offending photo using EXIF tool: place the photos in a folder with exiftool.exe and run this command throuhg a batch file: exiftool -CSV *.jpg > PhotoExif.csv That will dump the full EXIF data to a csv file. I've noticed that the offending photos are missing several EXIF attributes. I've been using "OffsetTimeOriginal" missing as the barometer for which images are causing the issue, and running the screen shot work-around on those has been successful.

‎06-13-2022

@JamesTedrick is Esri aware of the issues?

‎06-13-2022

Well glad it's not just me, but unfortunate that we're all haivng issues. I finally had some jobs complete (I just let them spin for an hour) and there were multiple zip files generated. I'm wondering if something is multiplying each export job and overloading the servers?

‎06-13-2022

I've noticed that at times, submitting a featuire report job takes a very long time to finish (sometimes > 20 minutes). This is intermittent, but becoming more frequent. Has anyone else noticed this?

‎06-13-2022

Sorry for the slow reply. I've been working with Esri support and they're looking into it further. For now I'm stuck with the screen shot work-around, which has been a time-consuming effort. I did look at the EXIF data further (exporting the full data using EXIF tool) and found that the offending photos are typically missing these EXIF params: : ExposureMode, FlashpixVersion, OffsetTime, OffsetTimeOriginal, SceneType, SensingMethod. My guess is the time ones are causing a problem, but I hit a snap trying to fix the EXIF and gave up. So, if I have a bunch of photos I export them all, chekc ther EXIF data, and can narrow down which need attention to create the report. Hopefully this can be fixed sooner than later!

‎05-11-2022

This would be super helpful, I rely on the Inbox for a QC workflow and to send forms back to users for revision. Forcing a refresh to always have the latest version of a record would save some headaches.

‎05-06-2022

I have a survey with ~15 daily users. Most submissions have no issues, but there is one user whose forms randomly cause this error when generating a feature report. My work-around is to download each photo, screen shot it, and replace the attachment with the screen shot. Once that's done I can export the PDF. Obviously, this is less than ideal. I've inspected the EXIF data for many of these photos and cannot find what the problem is. This person is using a samsungSM-S908U device, most others are using some version of iOS or a windows surface. That's the onlynotable difference I can find. Anyone else with this issue?

‎02-15-2022

I agree with all of the above, plus supporting html & css would be helpful! As-is the guidance hint does not provide much more capacity for explaining a question.

‎08-27-2021

Ahh yes, it's an enhancement to return the previous functiuonality that was inadvertently broken in a release. Clearly not a bug! I can't find ENH-000138568 when searching the support site. Any indication on what release that was implemented in?

Online Status	Offline
Date Last Visited	‎03-20-2026 04:11 AM

My Ideas

Latest Contributions by RobBlash

Re: Filtering integers broken after October 25 2022 update?

Filtering integers broken after October 25 2022 update?

Re: Why is spell check suppressed in Chrome?

Why is spell check suppressed in Chrome?

Anyone else feeling the pain from the re-ordered "Close Survey" menu in the field app?

Restore the original "Close Survey" menu and add a prompt to confirm "Close and lose changes"

Re: Survey123 feature report error Cannot read property 'width' of undefined

Re: Creating feature reports is taking a long time

Re: Creating feature reports is taking a long time

Creating feature reports is taking a long time

Re: Survey123 feature report error Cannot read property 'width' of undefined

Re: Option to force update Survey123 Inbox when opened

Survey123 feature report error Cannot read property 'width' of undefined

Re: Enable a scrollbar in the guidance_hint popup to allow more than 5 lines of text

Re: Make hyperlinks in a popup appear in a default browser

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

Create a separate Field Mapping for the attribute ...

Allow "contains the text" or "starts with" filter ...