Editing Existing Photo Attachments (3.13) — How to add previously entered data in Watermark

NickShannon2

As for version 3.13, you can now attached photos to exisitng data.  Excellent.  Thank you Esri. 

I would like to add a watermark to the photos that has data previously entered (i.e. existing attribution info).

Here's my statement:

bottomLeftWatermark="Lat @[latitude]\nLong @[longitude]\nDateTime @[datetime:short]&size=30" bottomRightWatermark=${Defect_No_}

The Defect_No_ is the existing data. 

The statement above actually works, but I can't change the size of the Defect_No_. 

According to Esri's Tricks of the Trade :

Data from your form cannot be added directly in the bind::esri:parameters column. Do not attempt to include standard XLSForm functions within your watermark expression. The right way to do this is to first put together the watermark content in a separate question, and then reference that.

Because I'm working with exisiting data, I added a new field (DefectNo1) to my data to accommodate the calculateion step. 

For DefectNo1:    concat('Defect No:',${Defect_No_},'size=30')

bottomRightWatermark=${DefectNo1}

But this doesn't work. 

 

Any help appreciated.  

 

 

Anonymous User

Hi @NickShannon2,

Thanks for the additional information and screenshot, now I understand the problem. This is not related to editing surveys or the Inbox, this is a watermark configuration problem on any image questions.

What you are seeing is expected when you try to reference the value from another field as a component of a greater watermark statement. Due to the way the statement is compiled and processed behind the scenes, you can not combine the variable and size parameters together in the watermark statement. It must be done in another field to give a single text string, and then it can be referenced.

Please refer to the tip in the documentation here:

https://doc.arcgis.com/en/survey123/desktop/create-surveys/watermarks.htm#ESRI_SECTION1_4E32925B1D4B45C1ADD6DBD00CA88AD5

Therefore you need to do something similar to the following, and by using a hidden question and null field type, the extra question will not be visible to the user, nor stored in the feature layer, purely it is used for the calculation while the app is open:

I have also attached the example XLSForm i made. Hope this helps, from my testing it works great when adjusting the size.

Regards,

Phil.

 

Watermarks test.xlsx