Renaming images in bind::esri:parameters not working (web app)

[frfu794d]

Hello Everyone,

I use the survey123 web app for Vistitor employed photography with cellphones (participats are not logged in). I have the problem that many images have the same name, namely "image.jpg". I would like to rename the images during the participation according to an ID created for each participant and the question answered. There are options to do this, but they seem not to work for me.

I have created an hidden ID field for each participant with uuid() and would like to rename all images of the participant with this ID and the question name in the field bind::esri:parameters with fileName=concat( "ImageQuestionNumberOne",${id}). But this does not work. Depending on the Phone used by the participant, I get image names consisting of a random number, a number with the date or images with the name image.jpg.  I have the same Problem if i only use a string or other ID's to rename it.  Does anyone know what I am doing wrong? An example is added.

Thanks a lot!

[LMedeirosUI]

@Tiff The hyphen vs. underscore is something Connect may deal with fine, but the web app isn't supposed to. As in, Connect can deal with both, but the web app can't. Safer to just use the hyphen now that they've changed the format. 

When I was having version issues, they weren't solved until I could update everything to 3.17. I missed several interim iterations (because Connect on my mac is 3.13) and I hadn't tried the image upload since Nov 2022, so I don't know when it "broke" for me... but when I tried to upload images recently, I republished using a PC and 3.17 and went back to my mac to use the field app... didn't work. Tried to update the field app, but couldn't because the mac version only works on new macs with the apple processor. So it isn't just how it's published, but also the version of the field/web app running the survey. As in, everything everywhere all at once 😂 If you're worried about breaking your survey, you could just publish a simple survey with the filename function and test it.

I hope that works for you. It was super frustrating for me to have to jump through so many hoops to get a previously working survey to work again (I'm a big proponent of updates should not break existing things/backwards compatibility). But it's definitely reason for me to upgrade my computer, even if it means I'll have to run parallels to use Connect.

[frfu794d]

@IsmaelChivite  Thank you very much! The Problem was the Version of Survey123 Connect, now everything works fine.