Latest Contributions by DerrickWestoby

The tokens will expire automatically.  I don't think you can set them to never expire, but I'm not a developer so take what I say with a grain of salt.  For my (public) apps, I run this GP tool occassionally to update a URL field for my image attachments.  I've tried to schedule it to run automatically, but that never kicks off for some reason.  https://community.esri.com/t5/arcgis-online-blog/show-attachments-in-pop-ups-with-arcade/ba-p/890588 ... View more

1.  I've never changed this personally, even when creating a survey from an existing feature layer.  I can't help you out with that specific, but related advice -  Go through and set all of the esri field type and esri field length values for the existing fields in your feature service.  Whenever I created a survey from an existing service, I have to go through and set that stuff manually or else someone will inevitably make a submission and get an error because of field length.    2.  You can DISPLAY the existing feature layer in your basemap by adding the web map that contains it as "Linked Content" and then re publishing it (you have to publish the survey once before this becomes available).   You cannot interactive with the map though, it just acts as a basemap.   If you want people to "answer the form for the feature", you can use the INBOX to allow them to see nearby rain gauges and then click it to update them.  You'll see arrows and distance indicators, but they won't actually be displayed on a map.   If you want to launch survey123 from a map, you can construct a URL parameter that will launch your survey in edit mode for a specific feature.    Or, you could also use "Field Maps" to allow people to view it on a web map and then update the feature in a form entry just like Survey123.    ... View more

try this modified XLS instead (added row 9, changed row 8 calculate column).  I don't know if this is still true on the most recent version of S123 connect, but I think that using position(..) in an integer field won't (or wouldn't) update if a change was made.   At least in my currently published surveys, they -will- auto-update if I use a calculate type to pull the position, then update my hidden integer field from the calculate.    (Which you can still prevent by using once(position(..))  )     ... View more

Hi Kelin,  I don't fully understand your question, but it sounds pretty close to a few implementations I have and possibly an untested idea.  First off, your example (${vertices} + ${one_location}) won't work because you need to format the geometry string perfectly.  See this esri article, under "Defaults and expressions", for an example of the exact format this string needs to be in.  Example:   -37.842156723211474 144.95942945338243; -37.83554486071995 144.9726235713864; -37.85681405373047 144.98240735651922; -37.85954045531896 144.97715349053766   You want to use concatenate for this example.  If we assume that your ${vertices} field contains a perfectly formatted string of vertices and you want to add an additional vertex called ${one_location that is also perfectly formatted, you could do something like this in a calculate field and then point your geoshape calculate column at it: concat(${vertices},' ',${one_location}) (for reference, here's a functional calculate from one of my forms where I'm finding the min/max lat/lon value across a repeat to generate a work extents geoshape: concat(${max_lat},' ',${min_lon},';',${max_lat},' ',${max_lon},';',${min_lat},' ',${max_lon},';',${min_lat},' ',${min_lon}) IF You have multiple geo_____ questions in your survey - Make sure that the geoshape question where you are actually storing geometry and uploading to your feature layer is the FIRST geo____ question in your survey.  If you have other geo questions in your survey, even if they are set to <null>, make sure they're lower down in the XLS than the one that will be storying the geometry.  I had an issue a few weeks ago where this was preventing my geoshape from being pushed to the feature layer.    As far as the ability to let your users select which method they want to use, I've been brainstorming this as well.  The early forms that I had set up all require a photo attachment and the location of the geopoint (in a repeat) is set up to extract the image's geotags and use those (because I wanted to be able to use drone imagery).  The updated forms I'm working on just pull from the device's GPS instead.  I wanted to add the option to let people select which to use, but all of the implementations I've tried so far end up as a pretty clunky user experience.   Assuming that's a similar sort of situation for you, you're welcome to try out an untested idea that I haven't gotten to yet: 1. ${upload_geoshape} - The Geoshape that will ultimately be uploaded/used 2. ${select_method} - Select_one question that the user sees based on your options 3. ${method_1}, ${method_2}, ${method_3} - 3x different geoshape questions with bind::type set to null and the relevant column based on the user's ${select_method} 4. A calculate field that handles the IF statement and pulls the geometry from whichever selected method (and geoshape) that the user selects.    You could hide #1 in a collapsed group or something at the beginning of the form, and 2-4 would be in their own group.  The user would only see the select_one ${select_method} question initially.  When they select the option, the relevant geoshape question would appear.   The geometry they input would then be extracted by the calculate field (#4) and used to populate your ${upload_geoshape} question that the user wouldn't even see.   Again....that process is untested, but I'm pretty sure it'll work.  The only reason I haven't implemented it on my forms yet is because they're for field users to go out and collect a lot of points in a short amount of time and I'm trying to minimize clicks and button presses for them.  I know that most of them aren't going to want to be forced to select an option each  time and if I were to use a default option the ${upload_geoshape} question, I'd still have to ask them to hit the "recalculate" button if they changed it.  ... View more

Each OID will reference a single survey submission, so it makes sense that you only get the single report output.  You're trying to generate a summary report where OID=* and something like where=date_collected=today.    I have no idea how to do that via integromat with the built-in modules and configurations, but I assume you might be able to do it in integromat with a custom HTTP module.  If  you're comfortable using your browser's developer tools (F12) to view network traffic, you could probably go to the Survey123 website and manually generate your summary report of the day's activities just so that you can view the REST API call that it makes.   If you can find that, you should be able to fill it in the HTTP module and replace a few things with what's in the webhook payload (token, today's date, report template to use, etc).    Ismael posted a blog about setting up those HTTP modules to generate feature reports a few years ago, before Integromat had a ready-to-use module.   Actually,  I guess you wouldn't want to have it trigger off a webhook because you'll end up with duplicates if it's running per-submission.  Assuming you can even have an integromat scenario without having a webhook initiate it, it would probably be better to just set it up to run at the end of every day and handle the token generation and API call for report generation with HTTP modules.   Since it can be time consuming to try to set all of this up just to see if it works in the first place, I'd try constructing that summary report REST call and test it out in Postman before even messing with bringing it in to Integromat.  ... View more

 +1 for  AdminGIS2's recommendation, but a couple more points -   There was a bug in ArcGIS Pro where the Append tool would not maintain attachments when appending to an AGOL hosted feature layer.  This was resolved with the latest release (2.9.0 I think). Make sure you're using the latest version of ArcPro.  I was doing the same thing as you about 2 years ago and I think I ran into the same problem because I was using the "Export to FGDB" option to export the data (your "V1" data) in AGOL, which didn't export attachments (at the time).  Instead, I used "Create replica" and that resolved the issue for me.  ... View more

@Anonymous User - Your recommendations worked for creating the feature layer initially via Connect, but Survey123 is submitting geoshapes with null geometry if the geoshape question is moved to a row lower than a null geopoint after initial publishing.   My first geo question is a geopoint set to null, then I have a repeat with a geopoint in it, then a geoshape that's calculated from the min/max lat/lon values extracted from the repeat.   If I publish the survey with the first geo question being null, I end up with a table and an error message that matches the original poster of this thread.  Your recommendation to move the non-null geo question to the top for initial publishing fixes this issue.  If I do a test submission without changing this order of questions, the geometry for my geoshape is stored.  If I move it lower than the null geopoint (and the repeat that contains another geopoint), submission succeeds but the geoshape geometry is null.  If I move it back up to the top of the form, the geometry is included in the submission.  If I move the first null geopoint below the geoshape (and the repeat table), the geometry is once again included in the submission.    I've tried this a few times now, including publishing a new survey multiple times.  I also queried the feature layer to make sure it wasn't just an issue with the map viewing visualization.  I'm using Connect 3.13.234, fyi.  Pictures: 1. Query on first submission, OID1, before moving the non-null geoshape question at the top of the form.  2 & 3. Query on OID2 & 3 after moving the geoshape below the null geopoint.  OID2 is automatically created with my calculation. OID3 was a manually created polygon in the app. (extent_acres is one of my calcs on the geoshape, so you can tell the app is recognizing it) 4. Query on OID4, after moving the null geopoint to the bottom of the form (and under the repeat), making the non-null geoshape the first geo question in the form again.  Geometry is included on submission.          ... View more

Welcome, and I'm glad it helped you!  (Credit to  @IsmaelChivite and his awesome blog posts for teaching me how to do this in the first place) ... View more

You should be able to add it via the AGOL interface for the feature layer, too.  I've done this when updating published surveys with new select_one or select_multiple questions created from a new list.   (As others have said, back up your feature layer before doing this)   Update the list with the exact values you have in your list in the Survey123 XLS form.    ... View more

I'm sorry I can't help you on Power Automate specifically, but I can show you how I have it set up in Integromat if that helps.   It took me a bit to get this working in integromat as well.  Same setup as you, photos in a repeat.    The array I'm passing to the iterator is the repeat itself (field_observations)   Then I run the scenario once by triggering the webhook with a submission, so that now I can see the structure for the next module.  Here's where I'm grabbing the URL using an HTTP GET module   And uploading each photo to google drive, while renaming the photos. Note that in my scenario, I have to include the file extension when renaming.       ... View more

Was there any further info on this since the last post? I have the same question.  CSV file added via linked content and used in 6 different surveys. I update once a week (through the AGOL interface, replacing existing CSV with a new one using the same file name and column names).  I'm not seeing any of the forms updated with the new data (projects) in the CSV file, 60 minutes after updating the CSV.   I can see that the mobile app is downloading the new CSV when starting a survey due to the file size being reported, but the options haven't changed.  Same thing with the web form.  ... View more