Latest Contributions by Katie_Clark

Hello, I use several JavaScript functions in my survey to query features layers from the living atlas to auto-populate certain fields in the survey. (i.e. city and county name, etc) I'd like to also query the NWI layer, which is in the living atlas but is marked as "exclusive content for subscribers". Using the same type of script like I did for the other data returns {"code":499,"message":"Token Required","details":[]}, which makes sense since it requires a login to view the data. Is there a way to utilize the credentials that were used to login to Survey123 within a script so that I can query this layer? Thanks in advance for any assistance! ... View more

So, I've hit a huge roadblock that I wasn't expecting with Survey123... I created a complex survey to function as a replacement to expensive proprietary software so our company could use Esri products we already pay for instead of purchasing additional software. I got everything working in the Survey and Feature Report template, and thought things were almost ready for "launch". However, one requirement is that the user who submitted the survey (usually a Creator or Field Worker role with edit capabilities) needs to be able to view submitted records and possibly make edits to submitted data once they get back from the field (this is a functionality of the other software that we need to replicate). I told them "Oh yeah, no problem. You can edit records in the Data Tab of the survey123 website." I had done it many times before, so I didn't foresee any issues. However, today when the user attempted the workflow he mentioned he couldn't edit records. I looked into it further and noticed this message: Katherine_Clark_0-1649350395332.png   Then I found this documentation from Esri, that does specify that editing functionalities are not supported for records with nested repeats. Katherine_Clark_1-1649350490505.png Then I thought, "Ok, but maybe they can still edit in the data tab." I was able to make changes when clicking on a specific value in the table, and a colleague of mine tested it and it worked for her as well. However, it still did not work for the user who originally submitted the record (I assume this is because they are not an administrator type, and we want to keep it that way). So....one question is just WHY is a nested repeat a limitation for this? Is there any plan for supporting this functionality in the future? Is there any type of workaround I could do for this so that the user can edit existing records in a browser interface? Thanks for listening... -K @JamesTedrick @IsmaelChivite        ... View more