Latest Contributions by erica_poisson

‎12-14-2022

Hi - I am building a new Flow to update a feature layer based on the updates to a related table. The data is updated through Survey123, so I am using the Survey123 trigger in conjunction with the new ArcGIS Connector to "Update a record in a feature layer". I've set my condition so that the update only occurs when Update Type = Status Change, however I can not figure out how to only look at the most recently submitted related record. While this Flow is working well and my feature layer is being properly updated, I can't help but think there is a better way to do this... I just don't know what that way is. What I'd like to do is have the Flow only look at the most recently submitted related record via the Survey123 trigger. What is actually happening is that every related record is being assessed and the feature layer is being updated multiple times. Any suggestions would be helpful. Below is my current configuration:

‎12-14-2022

Hi @ZhifangWang - I have a case open with Technical Support now and I think I have identified what is happening here. My case number is #03216988 for your reference. I can share the Survey123 XLSForm with you, or invite you to a group that contains the Survey123 form, web map, ExB app and hosted Feature Layer I am working with, if that helps. My Survey123 form was working properly until early last week when I had this error. I republished the form and it was working OK again until I swapped out a layer within a web map and needed to update my Experience Builder app to re-configure the connection between the Map and Survey widgets. I am passing attributes & geometry from a layer in my map into a Survey123 form. I'd switched the attribute/geometry source layer in the map, and needed to rebuild the connection between Map and Survey widget in ExB. I was unable to do this because of the error this post was written about. After lots of testing, I think I have identified the problem as Survey123 Connect version 3.16.xxx. Yesterday, I republished my Survey123 form using an older version of Survey123 Connect that I had on my computer. I republished the XLSForm from version 3.15.175. Before republishing, I removed my pulldata @ layer function since this is not supported at version 3.15.xxx. When I opened my Experience Builder app, it was working perfectly and I was able to rebuild the connection between my Map and Survey widgets. I saved and published ExB. I then opened my XLSForm in Survey123 Connect version 3.16.110, added the pulldata @ layer function back in and published the form. I opened the published ExB app and was able to successfully use the map/survey together. The information from the map passed into the Survey123 form and I could submit. Screen capture below from right after republishing from Connect version 3.15.175. I am using this pulldata @ layer function in the XLSForm:

‎12-14-2022

Hi Zhifang - Yes; my form does contain a pulldata @ layer function. Republishing did seem to correct this particular issue.

‎12-09-2022

Hi - Cross posting in the Survey123 community to see if anyone has ideas on this error I am running into. I have an existing Experience Builder app that I need to update. Within ExB I have a Survey123 form and a web map. I am passing geometry and attribute from a layer in the web map into Survey123. This was working well, but I updated the source layer and needed to fix the connection in ExB to pass geometry/attributes from the new layer in the survey form. When I attempted, I received an error. Full details on error & screen capture showing error in this post - https://community.esri.com/t5/arcgis-experience-builder-questions/minified-react-error-31-in-experience-builder-when/m-p/1239601#M5879 Any advice would be appreciated.

‎12-09-2022

Hi - I am using Experience Builder to pass the geometry and attribute information from a feature layer in a web map into a Survey123 form I own. This had been configured and working well, however, I switched the "source" layer (source of the geometry/attributes) in my web map and need to re-connect the layer to my Survey123 form within Experience Builder to continue passing this information from the web map/selected layer into Survey123. When I go to re-configure the Survey element in Experience Builder, I see this error in the config pane on the right as soon as I try to make a connection between the layer in my map and the form. See screen capture below. Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Ben%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings. I have tested in Firefox and Chrome and see the same problem. Attached is a screen capture of the issue. In addition, this is occurring with a Survey123 form that threw this bizarre error out of nowhere on Monday. See this GeoNet post for details; I am unsure if this new problem is related to this error or if this is something different. I do have a technical support case open, but wanted to post here as well in case anyone had insights. I have republished a new Survey123 form, saved a new copy of the web map and tried creating a new Experience to see if this resolved my issue, however the error still persisted. Please advise,

‎12-08-2022

This would be extremely useful - please add to the road map!

‎12-08-2022

This would be massively helpful if it were possible.

‎12-08-2022

This would be massively helpful if it were possible.

‎12-08-2022

@RussRoberts - will it ever be possible to copy a layer between web maps? Say I want the same layer symbology & pop-up in another map - instead of painfully rebuilding it every time, it would be nice to copy it into a new map.

‎12-07-2022

@gismoe - thanks for the tip. I'd been afraid to republish just in case something else went wrong, however this fixed it!

‎12-06-2022

Hi - I have two Survey123 forms which I last published on December 1. I can confirm both forms were working well after being published. Today, I went in to the form and received an error: There are two versions of my Survey123 form - one for data entry and one for data updates. They both reference the same hosted feature layer. Both forms show this error when I launch them. One form is embedded in Experience Builder and the other in a Dashboard. As a note, there is not field or domain of just "T" in the forms. These forms and apps have not been touched since Dec. 1. Surveys were published via Connect version 3.16.106. Can someone please advise of this problem? Thank you,

‎12-01-2022

Hi - I am adding a watermark to a Survey123 image question. I want to reference attribute information from previous fields, so following instructions in this post (https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-photo-watermarks/ba-p/893593) and in the sample template available in Connect, I have added a null attribute field with a concat() statement and then referenced that new field in the watermark statement. As soon as I add text formatting into my concat() statement, the watermark ceases to work and doesn't show up on my image. Here is my concat() statement; this is set up as a null field type - Here is my watermark statement - there are a few, but it is the last bolded on which is relevant to this: As soon as I remove '&color=#730000&haloColor=white&size=14&margin=10&bold=true' from the concat() statement, the watermark shows up and works perfectly. I've tried replacing the single quotes with double quotes and have the same behavior. I want this watermark to be formatted in the same way as the one in the opposite corner. I am using Connect version 3.16.106. Any advice would be appreciated. Thank you,

‎11-29-2022

@IsmaelChivite - This is very helpful - thank you!

‎11-23-2022

@IsmaelChivite - Could the "@layer" function be used to locate the record with the most recent CreationDate (editor tracking field)? I was wondering if I could build a where query to return this... I've been doing a bit of testing with building the SQL query in Pro but am not having luck there. I was thinking something along the lines of... CreationDate = (SELECT MAX(CreationDate) FROM table) Could you provide any insight on this?

‎11-17-2022

On a call with Tech Support we were able to capture network traffic to get a more detailed error message. The additional details pointed to an issue with the group. After investigating the group, I discovered that when I'd initially created it years ago, I had set it up so that only group owners/managers could contribute content to the group. After changing this setting, I was able to successfully transfer ownership of the Survey123 form to a new owner. One aspect of this that is odd to me - I was able to transfer ownership of the feature layers (1 hosted and 4 views) without issue (to the same user). All 5 of these items are also shared with that same group, but did not throw an error. This error was only present with the Survey123 forms and report templates.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by erica_poisson

Update feature layer with most recent related record

Re: Minified React Error #31 in Experience Builder when connecting Survey123 form to Web Map to send data to survey

Re: Error initializing form... T is null

Minified React Error #31 in Experience Builder when connecting Survey123 form to Web Map to send data to survey

Minified React Error #31 in Experience Builder when connecting Survey123 form to Web Map to send data to survey

Re: Import Symbology to Hosted Feature Service or Hosted View in AGOL

Re: Copy/paste Web Map layers

Re: Copy and paste layers from one web map to other web maps in AGOL

Re: Duplicate Layer in AGO Web Map

Re: Error initializing form... T is null

Error initializing form... T is null

Watermark disappears when adding formatting via concat statement

Re: Survey123 Tricks of the Trade: pulldata("@layer")

Re: Survey123 Tricks of the Trade: pulldata("@layer")

Re: Unable to transfer Survey123 form to new owner

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...