Latest Contributions by erica_poisson

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

Hi William, I am very new to this, so I need to look into the SEDF. My goal is to just calculate the "Total Gull Count" daily. The field already exists in the Feature Layer. The layer is edited daily in Collector and I need to tally the counts of different gull species into one total value. The "Total Gull Count" field will be used in maps and Dashboard charts/indicators. I don't want to have to re-publish the data each time; I'd like to leave it alone where it is in ArcGIS Online.  For the code sample you provided above, this still does not work when I change the layer index to 1 (this is where the "Total Gull Count" field lives - all of the values being added together also live here). I get the error "index is out of range". Does this not work with a hosted feature layer's related tables? Thank you, Erica  ... View more

Hi Josh, I am hoping you might be able to help me out...I am trying to re-purpose the code above to calculate a field in a feature layer that has sync enabled. I am trying to do this in a Notebook in ArcGIS Online. Here is what my code looks like.. from arcgis.gis import GIS from arcgis import features from arcgis.features import FeatureLayer gis = GIS("home") gis = GIS('https://arcgis.com', 'xxxxxx', 'xxxxxx') Site_Inspections = gis.content.get("511646881336491988ab0b87817343ad") Site_Inspections Site_Inspections_lyr = Site_Inspections.layers[1] Site_Inspections_lyr.calculate(where="OBJECTID > 0", calc_expression=[{"field": "Total_Gull_Count", "sqlExpression" : "RB_numb + HG_numb + BB_numb + Unknown_Number" }])‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I keep getting the following error: --------------------------------------------------------------------------- IndexError Traceback (most recent call last) <ipython-input-12-b67e0c1245fc> in <module> ----> 1 Total_Gull_Count_lyr = Total_Gull_Count.layers[1] 2 3 Total_Gull_Count_lyr.calculate(where="OBJECTID > 0", calc_expression=[{"field": "Total_Gull_Count", "sqlExpression" : "RB_numb + HG_numb + BB_numb + Unknown_Number" }]) IndexError: list index out of range ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I've triple checked my feature service, and the layer I am attempting to do this calculate on is index 1. Does it matter that this is a table? Do you have any suggestions that could help out here? My goal is to schedule this to run daily to update the "Total_Gull_Count" field within my table.  Thank you, Erica  ... View more

Hi Ismael Chivite‌, I was curious if there were plans to allow surveys with nested repeats to be embedded in Dashboards w/ mode=view.  I have a survey w/ nested repeats that some managers want to be able to review for accountability purposes. I was hoping I'd be able to use a Dashboard to do this, so they could select a record and view the full contents of the survey in one easy-to-read window. When I attempt it, I get the message "This survey contains one or more nested repeats, which are not supported in the view or edit mode of the Survey123 web app."  The thought here is, managers can review submissions without having to export surveys to the custom report template.  The only other methods I've found for doing this involves a "List" and multiple "Details" elements in a Dashboard, which is not very user friendly or streamlined. I've run into similar issues with Experience Builder.  Thank you, Erica  ... View more

Yeah - this survey is a bear.  I was able to get this to work using the coalesce function. I've never used it before (or even seen it used before), but it was able to fix this issue. Inside of the repeat I added 31x3 'calculate' field types with the bind::esri:fieldType set to null, and bind::type set to int; then I used the coalesce function in the 'calculation' column. Outside of the repeat, I changed my sum calculation to sum(${coalesce}). Now that I see how it works, it seems like a very powerful calculation to deploy.  Thank you for all of your help with this!  ... View more

That is interesting to know. Even though I don't have a workflow like this now, it is good to be aware of. Thanks for sharing that! ... View more

This doesn't work. Without the relevant, even with a calculation in there fields show regardless of what is selected for the violation type. Like I said, with 282 fields, this just doesn't work.  Here is one portion of the survey's XLS: Here is what the survey looks like when previewing in Connect: I think that might illustrate why relevant statements are a must.  If you are referring to a calculate in the "type" column of the XLS...this also will not work because the user needs to be able to select a violation code - e.g. 2a1 - and enter a number. My calculation was set so that at the worst the field gets a value of 0 if the violation code isn't selected, and if violation code 2a1 is selected, the field get's a 1 that the user can then increase to represent the actual number of violations (sometimes there will be multiple -- one violation code could have 3 people = 3 violations).  I am using "type" = calculate outside of the repeat to sum up all values for one violation type in the repeat.  ... View more