Select to view content in your preferred language

Branch Versioned Surveys: Enable attachment keywords for image questions

630
2
08-21-2025 01:56 PM
Status: Open
AlfredBaldenweck
MVP Regular Contributor

Notes:

  • Not sure if this is a Survey123 Issue or an AGOL/Enterprise Issue, so please feel free to move it to the correct board. I assume this has repercussions for Experience Builder's new Feature Report Widget.
  • I have an open support case open for this that is resulting in an Enhancement. I will edit this to include the enhancement number when it is generated.

Related documentation: 

Idea:

I'd like to have branch versioned services get the correct attachment keywords. 
The reason for this is that we have moved towards Branch-Versioning to be able to make surveys from it, as opposed to traditional versioning. What we've found is that the Branch Versioned surveys do not print image questions because the attachments keywords are turned off.

AlfredBaldenweck_0-1755809277981.png

View of the feature service's JSON, showing keywords are disabled.

The end result of this is that the only way to print the attachments is by using the ${#$attachment} syntax, which gives all the attachments at once out of context.

Please give us the ability to print images in the correct context each feature's report by enabling the keywords in branch-versioned services.

 

 

2 Comments
DavidSolari

Does Upgrade Attachments not add the right columns and fix the issue? I have branch versioned datasets in my 11.1 setup and running that tool gets things working perfectly. That said, if the latest version of EGDBs don't create attachment tables with those 2 attributes under all cases I'd say that's a deficiency, it's a trivial thing that would save everyone a ton of time.

AlfredBaldenweck

Update: Upgrade Attachments being run on the table prior to publishing the service did, in fact, fix this issue.

I've logged an Enhancement:  ENH-000179432: Apply the Upgrade Attachments workflow automatically when publishing a survey to a branch versioned dataset.

Reason being that if this is going to cause a problem, it should just happen automatically to prevent the problem.

 

This can probably be marked Closed, I guess?