Latest Contributions by IsmaelChivite

The map control in Survey123 does not have a coordinate-input method you can use to update the coordinates of a vertex in a polygon or line.  This could make a good ArcGIS idea for consideration. As an alternative, what about the approach described in the animation below? Essentially, you ask people to enter the coordinates of the vertices, and you dynamically build the polygon or polyline on the fly.   Attaching the XLSForm so you can play with it and see if that would work for you.  ... View more

@MarikaVertzonis  ... View more

I think using a note type will help here. Screenshot below + example XLSForm. A couple of topics that could help: https://doc.arcgis.com/en/survey123/desktop/create-surveys/xlsformnotes.htm  https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-quick-guide-to/ba-p/1101322 https://community.esri.com/t5/arcgis-survey123-blog/understanding-notes-in-survey123/ba-p/894937 ... View more

Thanks for your question. This is not something that has come up much in the past, so we haven't paid attention to it. May be you can describe the use case in some detail? I am interested to learn about it. The time control does not currently allow you to enter seconds. As a workaround, you could use an additional integer question. I guess it is not ideal, but can't think of a better way to do it.   ... View more

Below is an example: Configures the Inbox to retrieve only records where the date value in the install_date column is now older than a week from the current date.   ... View more

Use the resultRecordCount parameter to get only one record from your table. resultRecordCount combined with orderByFields, will let you get the most recent. For example: ${#myRepeat | orderByFields:"inspectionDate DESC" | resultRecordCount:1}...${/} ... View more

Hi. See attached XLSForm and corresponding Report template. To test this, publish the XLSForm making sure the name of your survey form is BugsAndEnhancements v2.  If you choose a different name, then you will need to edit the template to reference your survey name accordingly. Highlights: I used a summary section. For details on summary sections, check this blog or this help topic. I made extensive use of !important.  If you add !important to the end of a where statement, the report service queries the entire layer, as opposed to just the records passed to the report task.  Here are some examples: ${BugsAndEnhancements_v2 | where:"category = 'Bug' and submittedOn BETWEEN CURRENT_TIMESTAMP - 7 AND CURRENT_TIMESTAMP !important" | stats:"count,objectid"} ${#BugsAndEnhancements_v2 | where: "category= 'Bug' !important" | orderByFields: "submittedOn DESC" }... ${/} The idea here using !important is that your report will ALWAYS query the entire survey layer and get back records in the last 7 days.  !important will override the records passed to the report task. In PowerAutomate, you can harcode the ObjectID parameter of the Create Report action and say, for example, 1. !important will ignore the ObjectID and work with the entire table. This worked pretty good for me. I was able to schedule this and have the report run as expected. Hope it helps. For context, you can go about scheduling reports in a couple of ways: In Power Automate, you can use the WHERE parameter in the Create Report action to dynamically pass the records against you want to run the report. I think this is how you originally approached this. Unfortunately, this will not work today, because of a BUG, although we will fix this in our upcoming June release. Alternatively, you can use the !important approach I describe above. In this case, as I said, the WHERE and ObjectID parameters in the Power Automate Create Report action will be ignored. In your particular case, since you want to always create a report for the past 7 days, I think this approach will do the trick. We will cover all of this in more detail in our upcoming Automate Survey123 Reports webinar.  Hope you can make it.   ... View more

I think it is doable. Simply add the extra fields you need into the related table and populate them using URL parameters. You can send this info via the link you include in the popup. In the original survey you can calculate these extra fields as you already do. In the second survey, the one pointing direcltyi to your related table, these fields will not be calculated. Instead, you populate them with URL parameters when the form is loaded. ... View more

Thanks @rsun_TQB  Switching status to implemented. ... View more

I agree with @JoshuaSharp-Heward  If you use the repeat_count column, you are essentially asking Survey123 to automatically add 6 records into your repeat. Since you have required questions in the repeat, the respondent must complete them all. What @JoshuaSharp-Heward suggests gives you the option to add as few records as you want, but every record must be complete. I am attaching below an example and including an animation for clarity.   ... View more

Hi @EvanDarpini  I think a JavaScript function will be perfect for this. For example: function squareRootOfSumOfSquares(nums) { let sumOfSquares = 0; let numsArray = nums.split(','); for (let i = 0; i < numsArray.length; i++) { sumOfSquares += numsArray[i] ** 2; } const squareRoot = Math.sqrt(sumOfSquares); return sumOfSquares; }   The function takes a comma separated list of numbers, squares them all one by one and calculates the sum. Then it returns the square root of the sum. You can generate a comma separated list of numbers in different ways. Below is an animation showing the test I did with all of this. I created three experiences to enter the data. One using a single text question, a series of questions and a repeat. Just for fun.  Attaching a the XLSForm illustrating the concept.  If you are not familiar with JS functions check out this blog.  ... View more