|
POST
|
Still no effect if you change the value to something like 1280?
... View more
01-25-2022
10:37 AM
|
0
|
0
|
1904
|
|
POST
|
How about join()? Inside of my repeat, I have 2x hidden fields that construction a label string to summarize all collected samples (One of which filters to features that have a group assigned). Outside of my repeat, I'm using the join() function to summarize all repeat records in a note. (outside of repeat) note | summary_asbestos | Summary of samples collected: | concat(join("<br> ",${sampleString_asbestos})) (Inside of repeat) hidden | sampleString_asbestos | Returns a string to summarize all asbestos samples collected | concat(${entry_ID_asbestos},' - ',${material_code_asbestos},' - ',${description_asbestos},' - bld',${building_asbestos},' - flr',${floor_asbestos},' - rm',${room_asbestos},${populate_samplegroup_asbestos}) The calculation for the field that's only including records with a group entered: if(${sample_group_asbestos},concat(${entry_ID_asbestos},' - ',${material_code_asbestos},' - ',${description_asbestos},' - bld',${building_asbestos},' - flr',${floor_asbestos},' - rm',${room_asbestos},${populate_samplegroup_asbestos}),'')
... View more
01-24-2022
09:36 AM
|
0
|
1
|
1957
|
|
POST
|
In the "parameters" column, do you have a max pixel size set? I noticed something similar when I started using this just last week.
... View more
01-24-2022
09:27 AM
|
0
|
2
|
1921
|
|
POST
|
Not necessarily, no. You could handle exporting a CSV for only the newest repeat/inspection entry a few different ways, but using the "Export Data" option in your item details page is going to export the who dataset at once. If you ONLY want to show your most recent inspection in a CSV, here's some off-the-cuff ideas. Put a table in a word document to use as your feature report template and then filter the portion that prints out your repeat. (Something along the lines of only printing max(${$inspection | getValue: "position"} or ${if inspection_status='new'}${inspection}${/}. (I know the latter example would work in the feature report if that's way your workflow is set up. Not sure on the first example, but you could handle that in the form itself too). This process would make it so you can just copy the table out of the feature report and past into a CSV file. If you're not all that confident with any of the other recommended workflows, this is probably one of the easier ones to get working. Display your results in a dashboard and enable CSV export. (Layer 0 is your bird box/geolocation info and is displayed in a "list" element. Layer 1 is your inspection table and displayed in a "list" element. Selecting a bird box in the first list filters the inspection table in the 2nd list, which has the option to export directly to a CSV built into it. Filter to the most recent inspection by default, or let people flip a toggle switch to filter to the most recent inspection). This one is also fairly easy to set up once you have your feature layer published, but formatting the CSV a specific way can be a bit of a pain if you weren't thinking about that when you set it up. Use webhook automation (like microsoft flow or integromat) to auto-export a CSV on every survey submission. If you wanted, you could have it update a running tally spreadsheet each time, but also export a different CSV that only contains the most recent inspection. (I have a few surveys doing this now, exporting to a google sheets document that can be downloaded as a CSV) Connect to your feature layer in ArcGIS Pro and manually export selected records to a CSV as needed. That's just a handful of ideas, but it'll depend on how you want it to be set up. Making each bird box a feature on layer 0 and each inspection a record on layer 1 will automatically build a "relationship" between the layers when you publish it. This can make working with the data -a lot- easier in many cases, but slightly more difficult in a few I suppose. I try to give myself both options by copying over some of the layer 0 data over to my repeats behind the scenes. For instance: (integer)${birdBox_number} (integer)${birdBox_size} begin_repeat (hidden, integer field type)${birdBox_number_copy} = ${birdBox_number} (hidden, integer field type)${birdBox_size_copy} = ${birdBox_size} end repeat This way, I have the built-in relationship and can link dashboard actions with stuff like GlobalID & ParentGlobalID and restore backups easier, but I also have a simple, human-readable spreadsheet for layer 1 that I can use easily for simple tasks.
... View more
01-24-2022
08:15 AM
|
0
|
1
|
2924
|
|
POST
|
How about a survey with a repeat (allow adds, but read only access for existing) + inbox? Layer 0 - Bird box location, description, etc. Layer 1 - Your repeat where each repeat record represents an inspection. Users can use the inbox to find the bird box closest to them, open it up and view existing records, and then add a new inspection.
... View more
01-21-2022
08:09 AM
|
1
|
3
|
2941
|
|
BLOG
|
An observation & a question: Observation - The Paragraph->Line and Page Breaks->"Widow/Orphan control" setting was causing problems for me when it was toggled on. My photos were restricted to a max height that should allow 2x rows of photos and the preceding tables to display on a single page, no matter if they were portrait or landscape. I kept getting the table on one page and my photo(s) on the next page though....even if they were able to fit. Unchecking this option fixed that issue for me. And a question for @IsmaelChivite or @JamesTedrick - Is it possible to use a combination of ${image | getValue:"width"} and orderBy with this? I'd like to print out my photos with portrait orientation first and landscape orientation second and figured I'd accomplish this by printing them out in order of pixel width. (All photos are taken in-app, not attached, so I'm not too worried about mixed image dimensions being attached). I'm trying to do something along these lines, but haven't been able to get it working yet: ${#image| orderByFields:"image | getValue:"width" ASC" } ${$file | size:0:0:660:600} ${/}
... View more
01-20-2022
02:20 PM
|
0
|
0
|
44659
|
|
POST
|
I just came here to post this idea too. Just to make sure I'm asking for the same thing, here's the general idea: This is currently possible with the feature report syntax: ${ proj_extents_geoshape | drawingInfo:"currentLayer"| mapSettings:" b2519fd7a45647a0946f50b0535b6ddd" | size:175:250:0:0} and I would like something like this available in the feature report: { proj_extents_geoshape | drawingInfo:"currentLayer"| mapSettings:" b2519fd7a45647a0946f50b0535b6ddd" where:ParentGlobalID=${pguid} | size:175:250:0:0} Currently, I have the referenced basemap set up to filter points (geopoints contained inside a repeat) to only be displayed if they have been edited in the last 15 minutes. This works well enough for most submissions when the report is generated automatically via the integromat process. If I have to generate reports manually (such as someone submitting a partial survey, then editing it and resubmitting later), first I need to open the web map and change the filter to filter all points to the layer 0 record's GUID. There's other use cases I can think of where URL parameters being available in the feature report would be very helpful, but this seems like the most common one.
... View more
01-13-2022
11:17 AM
|
2
|
5
|
4398
|
|
POST
|
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
01-11-2022
09:21 AM
|
0
|
0
|
946
|
|
POST
|
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
01-11-2022
09:02 AM
|
2
|
0
|
11753
|
|
POST
|
@BenBlowers2 wrote: Hi all, I am creating a very simple summary report for all my photos. I would like each row in the summary to have a new number, "1", "2", "3".. etc... I cannot use objectid, as this numbering system is sequential and wont ever start at 1, 2, 3 etc. Is it possible to have a new unique numbering system for summary rows within a report template? Thanks, Ben Agree with Katherine's post. You could calculate the integer field with something like position(..) if you're using a repeat. It will auto-increment based on the repeat record, but it will not watch out for duplicates (for example, if you have 12 entries and delete #8 and then add a new record, you'll have two #12s). edit: actually, it looks like you can access the position of a record in a report now without having to store it as a field. ${#defects}
${$feature | getValue: "position"}
${/} https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereporttemplates.htm
... View more
01-11-2022
08:48 AM
|
2
|
0
|
3898
|
|
POST
|
If the feature layer is secured, I'm assuming the submission is from a named user account and not anonymous? You can grab the token right from the watch webhook module in integromat: To download the photo, add ?token=[token] to the end of the image URL This example is downloading attachments (in a repeat) via an iterator and then uploading them to google drive. I believe you can add them to an email one by one as well, but I haven't tried that. FYI - My integromat emails are limited to 3mb and I THINK that's a limitation of Integromat overall. It might just be my Outlook365 email, but I have a 20mb cap on that account and I seem to remember having the same 3mb limitations with Gmail and Outlook both.
... View more
01-11-2022
08:40 AM
|
2
|
2
|
2329
|
|
POST
|
Yes, it's possible to display a different basemap (and geometry styles/symbols) in the feature report. See the feature report syntax here - https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereporttemplates.htm Example: ${project_extents | drawingInfo:"currentLayer" | mapSettings:"271be24809ea473e9eb7d31579563e85"| size:600:550:0:0} "currentLayer" means that the symbology set in my feature layer's "Visualization" tab will be used. The quoted string after mapSettings is the itemID for the web map that I want this geoshape to be rendered with. Assuming that you have a field with something like ${floor_number}, you could make your feature report use a specific web map to print out all responses on floor 1, a different web map to print all responses on floor 2, etc. ${#repeat_name}${if floor_number='1'} ${sample_geopoint | drawingInfo:"currentLayer" | mapSettings:"itemIDofWebmapWithFloorPlan1"| size:600:550:0:0} ${/}${/repeat_name} ${#repeat_name}${if floor_number='2'} ${sample_geopoint | drawingInfo:"currentLayer" | mapSettings:"itemIDofWebmapWithFloorPlan2"| size:600:550:0:0} ${/}${/repeat_name} You could also do something like calculate the extents of all geopoints on floor plan 1, pass that on to a geoshape question to calculate the extents, and then render that geoshape with a webmap containing all of your collected points (filtered to floor=1). Here's a few examples from reports using different parts of what I mentioned above:
... View more
01-10-2022
05:30 PM
|
2
|
0
|
1468
|
|
POST
|
You are trying to print a single table for your entire report, and that table has a pre-set list of values that you want a check next to if ANY record in your repeat's related field contains, correct? If that's correct, I think there's two ways to do this. 1. Don't reference the repeat in your feature report. Instead, have a hidden field in your XLS form (outside of the repeat) that returns a 1 if that value is entered and a 0 if not. You'd have to do this for every option that's possible. This way, you could reference the questions outside of the repeat and not worry about your table itself repeating for each record in the repeat. 2. Use the repeat summary/aggregate functions, along with a little bit of funny business in your feature report itself. ${REPEAT_TABLE_NAME | where:”YOUR_VALUE = 'A1' " | stats:"count,objectid"} The example above will reference a question in your repeat (and does not require the open/close tags for repeats) and will return a numeric value of how many repeat records have 'A1' selected. Maybe you just want to print that number out instead of a checkbox, maybe not. If not, you could highlight that entire formula and change it to black text with a black background. It won't be an actual checkmark, but you could give the appearance of a solid black box for non-zero values. You'd still need to add an IF statement to only return values greater than 0, though (since this will still return a 0 for empty values). But it'll allow you to access the counts in a single table without repeating the table for each. Check out this article for more information on the Aggregate functions in the feature report - https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereportqueries.htm
... View more
01-10-2022
05:13 PM
|
1
|
1
|
5362
|
|
POST
|
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
01-10-2022
04:55 PM
|
1
|
2
|
3339
|
|
POST
|
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
01-10-2022
04:31 PM
|
0
|
0
|
780
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-25-2025 01:37 PM | |
| 1 | 11-18-2021 11:59 AM | |
| 1 | 08-06-2019 07:41 AM | |
| 1 | 11-16-2022 08:32 AM | |
| 1 | 11-15-2022 12:48 PM |
| Online Status |
Offline
|
| Date Last Visited |
07-11-2025
11:41 AM
|