|
POST
|
@AwesomeEvan - I've direct messaged you with the old version.
... View more
02-01-2023
05:16 AM
|
1
|
0
|
8533
|
|
POST
|
I have not heard back at all regarding this bug. I did just check in my My Esri portal and it says "under review". but no additional details have been added.
... View more
01-30-2023
05:22 AM
|
1
|
2
|
8561
|
|
POST
|
@SeanKMcGinnis - thank you! Will there be any sort of announcement made when this is available in GCC? Also, will any change be necessary to existing flows for this to take effect? Thank you!
... View more
01-18-2023
12:57 PM
|
0
|
0
|
3745
|
|
POST
|
Hi - I know Esri has been working with Microsoft to extend the token life from 14 to 90 days with the ArcGIS connector. When will that be implemented? I'd thought it was included in the December release, but am finding I still need to refresh tokens every 14 days. I may have misinterpreted what I read. Any insight would be appreciated. Thank you,
... View more
12-28-2022
08:50 AM
|
0
|
15
|
5273
|
|
POST
|
Hi - This has been logged as a bug - BUG-000154551 - via my Technical Support case. Please see this GeoNet post for full details on the problem and workaround. Workaround summary: The workaround is to publish from an older version of Connect (I used 3.15.175), set up Experience Builder w/ a Map & Survey widget to "send data to survey", save & publish the Experience, add the pulldata @ layer calculations back into the XLSForm, republish from Connect v 3.16. The Experience will continue working if these steps are followed.
... View more
12-16-2022
06:00 AM
|
1
|
0
|
1265
|
|
POST
|
Hi @ZhifangWang - This has been logged as a bug - BUG-000154551 - via my Technical Support case. The workaround is to publish from an older version of Connect (I used 3.15.175), set up Experience Builder w/ a Map & Survey widget to "send data to survey", save & publish the Experience, add the pulldata @ layer calculations back into the XLSForm, republish from Connect v 3.16. The Experience will continue working if these steps are followed.
... View more
12-16-2022
05:57 AM
|
2
|
4
|
8716
|
|
POST
|
Hi @SeanKMcGinnis - Thank you for the quick reply... 1. DCR File Number is one of the unique identifiers, however the relationship is based on a GlobalID/GUID relationship class. 2. So, would I modify my Flow so that I first have the ArcGIS Connector "Get data from feature layer", right after the Survey123 trigger? Is there where I could use the Where clause to set up this query? I am not really sure if I understand how to inspect the dates for all related records within the context of these new connectors. If you have additional steps/details or even a sample Flow or workflow I could look at, that would be massively helpful. Thank you,
... View more
12-14-2022
09:37 AM
|
0
|
3
|
2473
|
|
POST
|
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:
... View more
12-14-2022
05:28 AM
|
0
|
6
|
2513
|
|
POST
|
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:
... View more
12-14-2022
04:46 AM
|
0
|
0
|
8721
|
|
POST
|
Hi Zhifang - Yes; my form does contain a pulldata @ layer function. Republishing did seem to correct this particular issue.
... View more
12-14-2022
04:36 AM
|
0
|
0
|
2307
|
|
POST
|
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.
... View more
12-09-2022
05:13 AM
|
0
|
1
|
1339
|
|
POST
|
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,
... View more
12-09-2022
05:09 AM
|
0
|
17
|
11239
|
|
IDEA
|
This would be extremely useful - please add to the road map!
... View more
12-08-2022
06:02 AM
|
0
|
0
|
2396
|
|
IDEA
|
This would be massively helpful if it were possible.
... View more
12-08-2022
05:56 AM
|
0
|
0
|
697
|
|
IDEA
|
This would be massively helpful if it were possible.
... View more
12-08-2022
05:55 AM
|
0
|
0
|
1407
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 09-06-2022 09:14 AM | |
| 6 | 10-24-2024 12:04 PM | |
| 1 | 04-28-2021 09:14 AM | |
| 3 | 09-06-2022 11:53 AM | |
| 1 | 01-17-2024 05:18 AM |
| Online Status |
Offline
|
| Date Last Visited |
02-14-2025
01:16 PM
|