Latest Contributions by erica_poisson

‎10-25-2021

Hi Phil, So, my XLS has keywords (the 'name' parameter is/has always been present since the XLS was initially published), and I am using the following query statement in the begin repeat row of the bind::esri:parameters column: query allowUpdates=true I am not using any query statement in the Image row(s) however, and after re-reading the documentation I am unsure if maybe that is my problem. Specifically here, under Images in the second paragraph, it states that if I do not want users to be able to add new images, I should add a query statement "allowAdds=false" in the bind::esri:parameters column. Also, these images have mostly (probably all) been added directly from the Survey123 field app on each end user's iPad, although there could be a mix of the users taking photos with the camera and attaching photos via the "file" option. However...I did just republish the data because I needed to make some schema changes before I could make some updates to the survey. Would this impact the ability of the photos to show in the Inbox, even if they were all originally captured via the field app? See here for example of XLS Form parameters - this is the main repeat: This is the nested repeat: Thank you for the help.

‎10-22-2021

Hi Phil, I am trying to test this now. I just republished the survey at v. 3.13.234 and my field app is also at v. 3.13.234, however I can not view images when opening a record from the Inbox. I've refreshed the Inbox and I know there is an image...however it doesn't show up. The image is within a repeat. Would that affect my ability to see it? Thank you,

‎10-15-2021

@Anonymous User - I am making my way through your blog on how to set this up. I am curious how I would update the "Parse Edits" step's JSON to include specific attributes from my feature layer. Ideally, I'd like to set up the email so that it dynamically includes attribute information. I guess I am thinking like what I am able to do if I set up a webhook for Survey123. Here is an example of what I am talking about: I've done this for a different webhook where a survey triggers an update to another hosted feature layer. I have been comparing your JSON from the "Parse Edits" step with the JSON I use in that other webhook and just can't figure out where I'd insert something similar to call specific fields. In my other webhook, I use the following JSON to call specific attributes from the feature layer: { "type": "object", "properties": { "objectIdFieldName": { "type": "string" }, "objectIds": { "type": "array", "items": { "type": "integer" } }, "WR_Case_Number": { "type": "string", "items": { "type": "string" } }, "Inspection_Date": { "type": "string", "items": { "type": "string" } } } } I don't have a ton of experience in how to work with JSON, so any advice would be appreciated on where I should insert this within the "Parse Edits" step. Thank you,

‎10-04-2021

Hi @Ruth_JiatengXu, I am having a similar issue. It actually appears to be intermittent, but I can't determine the cause. This report template has been around for a while. Last Friday we were having issues so I updated the template to use a smaller map scale. That seemed to temporarily fix it, but we are now seeing the same error again today. This report generates just fine when the condition in the template is not met and a map is not included in the report. Here is the error: Attached is the report template. Any assistance would be great. Thank you,

‎10-01-2021

@Anonymous User I just went into Testflight and I am still seeing build version 3.13.229. On the EAC, I see version 3.13.234, but I do not see this in Testflight. I haven't done a beta test in awhile, but think I am doing things correctly...? I just read the fine print and see it can take 24-48 hours for the new build to be approved by Apple and appear in Testflight. Sorry! I can't figure out how to delete this...

‎09-30-2021

@Anonymous User Thank you for that really detailed information. The user who reported this is using a new iPad Mini. The workflow is for our Conservation Easement monitoring and she had me size the photos for the report template so that all of our monitors didn't have to manually re-size full-sized photos once exported to Word. This is the syntax I am using within the report template right now: ${ Related_Table_Photo_Information.Image | size:450:0} With that sizing, it came in so that we could fit two images and tables per page of our report, which is our organization's standard for these reports. Here is what the photo section of the report looked like pre-3.13: Here is what it looks like post-3.13 (iPad Mini): When I go to the Survey123 website and visit the 'data' page for this survey, I save the image by finding it in "form view", I click to view and then I click the download option in the upper right corner of the image. When I bring this into a report manually, I still can't replicate the size because the aspect ratio is different. Personally I don't think this is a huge deal. It doesn't seem like there is much we can do about this if this was a fundamental change to how Survey123 deals with the camera/photos. It seems like I might want to play with the sizing I specify in the report template to see if I can get the photos to not look squashed. I will pass on the great information you shared above to my user. Thank you, Erica

‎09-29-2021

@Anonymous User - With this new version, was there also some sort of automatic, behind the scenes change to photo attachment sizes? We have a survey which has not been republished at version 3.13 (it was last published with version 3.12 on August 16, 2021), however users are reporting a change in photo attachment sizing. We compared photo dimensions from before we updated to 3.13 and from after we updated. Pre 3.13 photo dimensions were 1920 x 1440. Post 3.13 upgrade and photo dimensions are 1920 x 1080. This is resulting in some squashed looking photos in our report template and when we export the full/original photo from the Survey123 website. The only change is that our MDM has updated all devices to Survey123 v. 3.13. Is there a way we can get back to the dimensions of 1920 x 1440? Any assistance would be appreciated. Erica

‎09-28-2021

@Anonymous User - I just opened an Esri support case and sent in the XLSForm for the survey experiencing the most issues. I sent you a direct message with the Esri Case # in case this is useful. Erica

‎09-27-2021

Hi @IsmaelChivite We're find that there are some new buggy behaviors and slowness with this new version. Specifically on sending surveys from the Inbox. The "send" operation seems to get hung up towards the end of 15-20 seconds with a semi-transparent screen over the top of the survey. Occasionally the survey fails to send and gets stuck in the Outbox. It requires repeated attempts to send successfully. I did a small and probably not thorough enough test before updating the software/survey. My biggest concern was ensuring that the calculations throughout the survey worked properly (which they do). I didn't anticipate issues with sending. This survey has nested repeats, lots of hidden calculations and is edited from the Inbox throughout the day. Any recommendations would be apprecaited. Erica

‎08-24-2021

@Anonymous User thanks. It looks like that might be a Premium connector that my organization has not approved to appear in our list of connectors within Power Automate or I am not seeing it appear when I search the Connectors). I will look for your blog sometime over the next two weeks to get more details before making a request to add this connector into our tenants.

‎08-23-2021

@Anonymous User - thank you! I currently use Power Automate with Survey123... I guess I am just curious what the trigger would be here. It's exciting this will be possible now!

‎08-23-2021

@Anonymous User - When will support in Power Automate be available?

‎08-20-2021

Hi @JakeSkinner - This is great. Is there any way to do this en-masse for many fields within one expression? Right now I am getting ready to write this expression & HTML code ~90 times for all of the fields I need to deal with. Thank you!

‎08-12-2021

Hi @GlenShepherd , I did create a new idea - https://community.esri.com/t5/arcgis-online-ideas/offer-official-support-for-removing-related-tables/idi-p/1088567/jump-to/first-unread-message Thanks for your help around this issue. I would definitely love to see some improvements made so this is officially supported someday! Erica

‎08-12-2021

First, some background: We have a hosted feature layer (hFL) which is used in a variety of different ways. In total, there are 6 Views of this hFL; some views are internal and editable, while the others are public and have view definitions applied to limit the data which is exposed. This hFL was built to include a related table; within the table we can record unauthorized trail use/conditions when staff are in the area. This information should not be exposed to the public. I had reached out to Esri Customer Care to determine if there was a way to remove a related table from a hFL view --- they replied that yes this was possible by going to the View's admin rest endpoint to use the "delete from definition" tool. I was told to add in the following snippet of JSON: { "layers": [{ "id": 1, "relationships": [{ "id": 0 }] }] } Once done, the hFL view no longer showed the related table. Awesome! After the fact, I learned that once you do this, you can not edit the pop-up (they basically break) and if you make schema changes to the original hFL (e.g. add a field or alter domains) they do not reliably trickle down to the hFL view that has had the related table removed. In some cases, schema edits come through fine, in other cases, they do not. There is also no way to undo the removal of the related table. The only option is to delete your View and start from scratch. My idea is this: In future releases of AGOL, it would be great to improve the View experience and make it fully support to hide or remove related tables from hFL Views. Right now the behavior is erratic and there is no way to undo this once completed (this was a huge problem for us since our public view is used in almost 100 maps). I think this would be useful to anyone who needs to share data publicly, but also limit access to internal-only information stored in related tables (e.g. inspections or something).

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by erica_poisson

Re: View Pictures of Submitted Surveys in Inbox

Re: View Pictures of Submitted Surveys in Inbox

Re: Use webhooks to automate workflows in ArcGIS Field Maps with Power Automate

Re: Help with a Survey123 report with multiple geometry questions

Re: Whats New in ArcGIS Survey123 (September 2021)

Re: Whats New in ArcGIS Survey123 (September 2021)

Re: Whats New in ArcGIS Survey123 (September 2021)

Re: Whats New in ArcGIS Survey123 (September 2021)

Re: Whats New in ArcGIS Survey123 (September 2021)

Re: Use webhooks to automate workflows in ArcGIS Field Maps

Re: Use webhooks to automate workflows in ArcGIS Field Maps

Re: Use webhooks to automate workflows in ArcGIS Field Maps

Re: Hide Field in Pop-up Using Arcade

Re: Feature Layer Views: Updating Parent Feature Layer Schema

Offer official support for removing related tables from hosted feature layer views

Re: June 2026 Update - No data No Selection text

Re: Category Selector RESET missing?

Image captions in sidecar

Add "Colorblind friendly" toggle option when selec...

ArcGIS Dashboard Data Expression, "unable to execu...