Latest Contributions by DeonLengton

Hi Liesl The issue is that you added repeats to the survey and the existing Feature Service doesn't have repeats. This causes a schema change (addition of related tables) and Connect needs to delete and create a new Feature Service. If you have existing data in the feature service then it should be easy to just export it to FGDB, publish the survey with the schema changes and append the data back into the main table of the new Feature Service. Hope that helps ... View more

Hi Lorraine One of our clients had a "similar" issue even though they were using Survey123 with existing pre-loaded data and wanted to use the Feature Report functionality. Turns out that you need to pay close attention to the tags ATT_NAME and KEYWORDS if you plan to use the Feature Reports with the existing data. I ended up using Python to create the Match Table CSV file and then importing those attachments with the AddAttachments_management function in Python. That seemed like the "correct" way to do it and then just making sure the keywords and attachment names were correct according to the question names. https://support.esri.com/en/technical-article/000027056 Not sure if this is relevant to your scenario but could be good to keep in mind, just in case. Regards ... View more

Hi I added an integer field (you can use a calculated field) inside the repeat: integer exotic_val Exotic Value   The calculation of this field check for exotic species being entered and use the category value if it is an exotic species. If it isn't an exotic species it assigns the value 0: if(selected(${Exotic_Sp}, 'Elaeagnus_pungens') or selected(${Exotic_Sp}, 'Microstegium vimineum'),${Exotic_Sp_Lvl},0) It uses the basic if syntax: if(condition, a, b) If the condition evaluates to true, returns a; otherwise, returns b.   Then just change your sum_Exotics3 calculation to: sum(${exotic_val})   I hope that helps Regards, Deon ... View more

Hi I simplified it and this is the result:   I hope that is the outcome you were hoping for. Here are the calculations: pulldata('permits','date_to_pull','name',${permit_number}) ${test_dob}+21*24*60*60*1000   The first one is still as you had it but i changed it to be a date type. date test_dob Date of birth   The second calculation adds 21 days to the test_dob date. Hope that helps. ... View more