Latest Contributions by erica_poisson

@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

I agree that this would be really nice - if I remember correctly, this was possible in Collector Classic.  ... View more

Thanks! That's a good workaround.  I will upvote your post when I can figure out how to do that in this new GeoNet...I gave it kudos...is that the new equivalent of upvoting?  ... View more

When editing a survey from the Inbox, is there a setting I can specify in the XLS so that the last record in a repeat shows? Currently when a survey is opened from the Inbox, it shows the first repeat record.  For example, a survey has 10 records in it's repeat. I want the survey to open at record 10, but by default it always opens at record 1 when refreshed from the Inbox.  Thank you! ... View more

Yes, that is what I did, but it did not work properly when utilizing the Inbox in the workflow.  You can also mix and match so set bind type to int and esri Field Type to null. Once I switched from esri Field Type = null to Integer, this workflow & the coalesce functions worked properly when a survey was edited from the Inbox.  Note: The combination you mention (bind type to int and esri Field Type to null) did work properly when completing the survey entirely after clicking "Collect".  ... View more

Hi Scott,  I am running into this issue now. Did you ever find a solution? I'd been able to successfully use this workflow with HFL in the past, pre Pro 2.6.  Erica ... View more

  @DougBrowning  -  I figured out a solution to this issue. In an attempt to cut down on attribute fields in my survey, the coalesce functions inside my repeat were 'null' field types. I changed this to integer field types to persist the data. Now my "exterior" (outside the repeat) coalesce functions work properly. The downside, is that I now have 94 additional attribute fields in my table.    ... View more

@DougBrowning  -  I am curious if you have any thoughts as to why the coalesce function does not work properly when a survey is edited from the Inbox. Our workflow is that someone starts a survey, sends it and edits it from the Inbox many times in a day. I've recently discovered that the coalesce function does not work properly when this happens. If I start a survey and then submit it and make no edits from the Inbox, it works perfectly.  This is a huge issue for us. If you have any thoughts on how to get around it, that would be great. Initially I thought it was due to the fact that my users were all in different versions of the Survey123 field app, but updating to 3.10 / 3.11 has not helped. My current thought is that I could use the Outbox instead of the Inbox, however I like the added security (data loss-wise) of using the Inbox. I haven't tested the Outbox yet, but hope to do this when I make my next batch of modifications to the survey.  Thank you! Erica ... View more

Hi Natalie & William, I was able to accomplish my goal using the following: import arcpy import pandas as pd from arcgis import features from arcgis.features import FeatureLayerCollection from arcgis.features import FeatureLayer from arcgis.gis import GIS # #### Run to process data: gis = GIS('https://arcgis.com/', 'xxxxx', 'xxxxx') # connect to feature layer and select proper table item=gis.content.get('a550ded747db465eb2ff62153b559095') l=item.tables[0] # need to deal with null Unknown_Number because Total_Gull_Count does not properly calculate if left null. unknown=l.query(where="Unknown_Number IS NULL").sdf # calculate null Unknown_Numbers to be equal to 0. print(l.calculate(where="Unknown_Number IS NULL", calc_expression={"field": "Unknown_Number", "sqlExpression" : '0'})) # calculate field Total Gull Count # select records where Total_Gull_Count is null, and then calculate value print(l.calculate(where="Total_Gull_Count IS NULL", calc_expression={"field": "Total_Gull_Count", "sqlExpression" : "RB_numb + HG_numb + BB_numb + Unknown_Number" }))‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more