topic Re: Survey123 repeat image question doesn't allow renaming if name already exists in the database. in ArcGIS Survey123 Questions

Survey123 repeat image question doesn't allow renaming if name already exists in the database.

Anonymous User — Wed, 05 Jun 2019 12:49:32 GMT

Why is my survey not allowing me to rename a photo in a repeat question with a name that is already stored in the related attachment table?

Background: I created my survey from a feature service. The feature class has related tables for repeat questions within the survey. There are two questions that are repeat image questions.

Problem Example: I was able to successfully submit a survey that contained 8 pictures that I renamed. The survey is for building inspections, so the example I'll use is I renamed one of the photos "Master Bedroom". I went to do another mock survey submission for a different property and when I tried to rename a photo for that house as "Master Bedroom", it turned red and reverted to the default name.

The weird thing is I went to the outbox and resubmitted the first survey. This meant that my attachment table in my database has two entries called "Master Bedroom" but the survey still doesn't allow me to rename photos that. Is there something I am doing wrong in my survey setup?

Re: Survey123 repeat image question doesn't allow renaming if name already exists in the database.

LaneFeschuk2 — Wed, 26 Jun 2019 21:43:26 GMT

Hi Adam, were you able to get any resolution for this? I am running into the same problem. Thanks.

Re: Survey123 repeat image question doesn't allow renaming if name already exists in the database.

JamesTedrick — Wed, 26 Jun 2019 22:50:00 GMT

Hi Adam, Lane,

Photos taken are stored in an application directory on the device and need to be unique- I would suggest adding the date or some other identifier to the file name.

Re: Survey123 repeat image question doesn't allow renaming if name already exists in the database.

LaneFeschuk2 — Wed, 26 Jun 2019 22:58:04 GMT

Thanks James, while trying to figure this out I had figured it might be specific to the device (even regardless of the survey being used?). For now we'll just have to use the default timestamp and work around with scripts.

Thanks again!