Latest Contributions by ZacharySutherby

Hey @HariharNepal,  Additional to @Neal_t_k's suggestion, you can change the WHERE clause in  feature_object_ids = i.query(where="1=1", return_ids_only=True, order_by_fields='objectid ASC') for j in range(len(feature_object_ids['objectIds'])): to be a specific survey.    `where=1=1` will loop through all the records in the feature layer and download attachments for each one. If you only want one specific survey record you could set the where parameter to something like:  where="objectid=1" - this will return just the survey record whose objectid is equal to 1 where="field_name = 'some_value'" - this will return zero to multiple surveys who have 'some_value' set in the attribute field called field_name You can get really intricate with the where expression, for more info see the Query (Feature Service/Layer) REST API doc topic.    ... View more

Hello @ChandraLala,  In Connect please select the Files button and open the file in your content folder called <yourSurveyName>.webform If the contents of your webform file is a JSON error message that says "Error: Entity expansion limit exceeded: #### > 1000", this is a known issue with the 3.25 release and is logged as BUG-000183859​.  If this is also what you see on your end please feel free to reach out to Esri Technical Support so you can be attached to the defect and track progress.   ... View more

Hey @IDEMuniMendoza,  Thank you for verifying you're seeing the issue in the web app! For the first issue where you're not seeing the calculations run I see you commented on https://community.esri.com/t5/arcgis-survey123-questions/webforms-not-running-calculations/m-p/1692926#M65730 I think this is the same issue. If you try setting calculationMode=always under the bind::esri:parameters column for your "f_sin" and "f_act" questions does that work around the issue?    On the second issue of data not submitting to the related table I don't believe I'm reproducing what I interpret as the scenario. I have a hosted feature layer with a parent layer and 3 related tables and when I create my survey based on that hosted feature layer the schema I see in Connect is: Which I believe is equivalent to your image 2. I removed table1 and table3 from my form design only leaving table2 and published the survey:    When I submit a record in the Survey123 web app I do see the related records come through in table2   A couple of things to cross reference:  How are your relationships configured? Are they GlobalID to GUID or GUID to GUID relationships?  Are you using a hosted feature layer, or a non hosted feature layer from ArcGIS Enterprise?  ... View more

Hello @IDEMuniMendoza,  Can you please verify when you are submitting surveys are you using the Survey123 web app or the field app?  On the second issue noted regarding the submission of related records is your survey configured with a submission_url?  ... View more

Hello @ArthurMartinez,  Did you author the survey in the Survey123 web designer or Survey123 Connect (desktop application)?  ... View more

Hey @RyanMullee,  Check out the Hydrant Inspection or Manhole Inspection for ideas on how to model your data schema. They both follow a similar idea where irrigation heads are hydrants/manholes in the samples and their repeats are equivalent to incident reports.  This UC presentation on Modeling Inspection Workflows may also be helpful.  Additionally while the terminology in this Tech Support KB article is quite dated the concept of the workflow is still relevant and very powerful.    ... View more

Hey @MatthewKing,  Try this link: https://earlyadopter.esri.com/key/TNRT%20RFFW%20JBT9%20NVQC Do you see a difference using that link? If so I'll update the links in this post and on the registration survey.  Thank you,  Zach ... View more

Hey @Carrie2025,  Try running your notebook using the latest 2.4.2 version of the ArcGIS API for Python. This was logged as BUG-000179345. It looks like you're running your notebook in a hosted notebook, unfortunately the current runtime version for hosted notebooks uses Python API 2.4.1. At this time to test in 2.4.2 you would need to download the notebook and run in ArcGIS Pro 3.6 or a standalone Python environment.  ... View more

Hey @ChristopherCounsell,  No additional requirements for relationships with other layers/tables not intended for use in Survey123. The thing to keep in mind is Connect has BUG-000120260 - Survey123 Connect for ArcGIS fails to publish a survey from an existing feature service when referencing a secondary related table, returning the error message: “Parent layer id _ not found for related table.” logged that is a consideration when building a schema intended for use as a submission_url in Survey123.  Where this would come into play is say you had a schema of:  Layer 1 Layer 2 Layer 3  Layer 1 has a 1:M relationship with Layer 3, and Layer 2 has a 1:M relationship with Layer 3.  If you want to author a survey where the form_id is set to Layer 2 and Layer 3 is a repeat in the form design, this situation will run into the defect above as when Connect triages the feature layer it will incorrectly assume it should be using the Layer 1 to Layer 3 relationship causing the error message to display.  ... View more