Latest Contributions by erica_poisson

Thank you! This was simple and elegant and worked perfectly. I really appreciate your help!  ... View more

I have sent this information via email - thank you! ... View more

@ZhifangWang  - I am seeing this error when attempting to generate a Summary Report now. My template uploads with no syntax errors. I can generate a sample report using 20 records, and it works perfectly. When I go to select all records (152), it fails with this generic error. I have tried this in both Firefox and Chrome with the same results. When I attempt with 130 records, it fails. When I tried it with a random number of records (56), it worked. erica_tefft_0-1617212818995.png   Is there a record limitation I am not aware of when generating these reports? How would I go about identifying the issue and resolving this? This issue was not present previous when I was initially testing and building this summary report template. This is the first time I have attempted to generate a report in 2-3 weeks.  This Survey also has an individual record report template associated with it, and that works without issues.  ... View more

As long as your relationship is defined before publishing the data to AGOL, you should be fine and the relationship will remain. I am not sure if the GlobalID/GUID values will be the same as what you've got recorded in your local fGDB though - that's something I have never checked.  ... View more

@FedericoRiet_Sapriza - I am way late to respond here, but in case you are still having issues, this is how I've dealt with a similar situation to what you're describing. Within a repeat I have 3 questions that could all be answered, or only one or two could be answered. Each of the 3 questions could write a value to one of ~93 unique fields depending on a previous selection. Then, to get a sum I use a series of coalesce statements within my repeat. Outside of my repeat, I then use a sum on the coalesced values. This works well and I would imagine it would also work for your mean calculation. I've included an example below.  Inside Repeat (integer type): Field 1 = Violation1aFirst (called w/ relevant statement) Field 2 = Violation1aSecond (called w/ relevant statement) Field 3 = Violation1aThird (called w/ relevant statement) Inside Repeat, to get valid value (calculate type): Field = CoalesceVio1a coalesce(${Violation1aFirst},0) + coalesce(${Violation1aSecond},0) + coalesce(${Violation1aThird},0) Outside Repeat to get sum across repeats (integer type): sum(${CoalesceVio1a})   This process results in a lot of fields within my survey (all hidden based on relevance or because "calculate" type). All total, I have 526 rows in my XLS form dedicated to dealing with these calculations.  ... View more

@DeonLengton   I have a few surveys where this is also an issue. I use a scheduled Python script to handle deleting these empty records each night, and that works well enough. It would be nice if a Minimal Compact appearance did work as you've described though.  ... View more

Is it possible to set a survey to open to the most recently added repeat when a survey is being edited from the Inbox? By default, the survey opens at the first repeat added. I'd like to be able to set the survey to open at the last repeat added (the most recent).  ... View more

@Anonymous User , I did not figure out how to do this within the summary report template, however I do use coalesce functions inside my survey to do this and that works well.  ... View more

Hi @KevinBurke, Thanks for the reply. I did try running the tool on the main hosted feature layer, and it did not work for the Views. I can try running it on my individual view layers to see if that helps. There are 5 view layers total, but only 1 of them is editable. The remainder are either public or have a view definition set to only show certain features for overlay visualization in Collector.  Will there be any downsides to running the tool? Could it potentially corrupt the view in some way? Thanks, Erica  ... View more

I would love to see this implemented in Field Maps. I do not think it would in any way replace Survey123 (there are just so many other things that make that fantastic), but it would be great to help streamline certain workflows if we could just use one platform (Field Maps) to collect data, like Roger mentions.  ... View more

Hi Ismael, This new update looks fantasitc - can't wait to try it out. On a related note - I am wondering if there has been a change to webhooks from Power Automate with Survey123. Previously, I was able to create multiple webhooks per survey in Power Automate. I'd created them in Power Automate and then see multiple webhooks listed in Survey123 > Settings > Webhooks. Now, when I create my second webhook it appears to 'overwrite' the original.  Is this a change in behavior for Power Automate?  ... View more

I am wondering if there has been a change to webhooks from Power Automate with Survey123. Previously, I was able to create multiple webhooks per survey in Power Automate. I'd created them in Power Automate and then see multiple webhooks listed in Survey123 > Settings > Webhooks. Now, when I create my second webhook it appears to 'overwrite' the original.  Has anyone experienced this? ... View more

Hi Kevin, If I use this tool on a hosted feature layer that has an editable View derived from it, will the effect "trickle down" through to the View so that my users are actually required to complete the required fields when editing the View layer? Thank you, Erica  ... View more

I am also interested in figuring out how to do this/if it is possible. It would be nice to be able to remove related tables from View layers when they contain information that is not appropriate/relevant to the public.  ... View more