Latest Contributions by EricaCirigliano

@JamesTedrick  I second Ole Olmanson's request for a pointer to documentation. Thank you! ... View more

@IsmaelChivite  I realize this is a very old thread, but the accidental deletion of content is an issue for us as well. Since I can't find any documentation for this, I assume there's still no way to disable the "x" button in the text box (which would force the end user to use the backspace button to delete content). Is there a poll I can take to ask for this as a feature? Thanks, Erica ... View more

Done! Thanks, @DougBrowning! ... View more

This is also needed when adding an image via the image::media column to a note. So many use cases!  ... View more

Hi, @DougBrowning, When you say "yes for sure," do you mean that this is possible? Or that you're agreeing with my suggestion to include select_ones as field types that will accept focus from the return key on the numbers keypad? I've read that adding the return key on the numbers keypad was a campaign you spearheaded, and it's a great idea. I just don't think the implementation is complete, because in a scrolling format on a phone (as opposed to a grid format on a tablet), tapping return from the numbers keypad can (and does, in our survey) skip over select_one questions until it reaches a field it can put the cursor in. Our users don't even know that the questions were skipped, as they trust that the survey is guiding them in the right order. Is this something you've encountered since the numbers keypad return key was implemented? Do you have a workaround? I agree with your ideas for tab order and navigating repeats. Our surveys have fewer repeats than yours, and are filled out by people who fill out such surveys only during field season and even then not daily, so data entry efficiency is not a high priority for us, though it's always nice. In the near future, my hope is for a better-implemented return key on the numbers keypad, or the ability to disable it so that it doesn't scroll users past survey questions. Thanks for all your hard work on behalf of the S123 user community. Erica ... View more

@ZacharySutherby  For the record, I'm a big fan of the dev teams behind S123 and QuickCapture. You all are responsive to requests and it's been gratifying to watch both applications mature in real time. This is the second time I've been asked to submit a bug report to help the S123 dev team. Unfortunately, the customer side of this is confusing to the point of being frustrating. The previous bug report appears, based on what our interface says, to be closed, but I know for a fact that the bug still exists. After spending 30 minutes trying to figure out how the process works, my supervisor and I gave up. If you, or anyone else in the land formerly known as Geonet, have pointers on how to get through this process from the customer side, we're all ears. Help us help you. Erica ... View more

@ZacharySutherby  Thanks for logging this as an issue. I'm not an administrator of our AGOL system, and I know internally we've been somewhat confused by the need to log a bug ourselves when it has been logged also by an Esri dev team and how to match those bugs up as being the same thing, but I will enlist the help of my supervisor and we'll take a crack at it. Erica ... View more

Hi @ZacharySutherby , Thanks for posting that. I was able to replicate the issue by changing the comparison operator from != to > in the choice_filter for the "action" select _one. Thanks, Erica ... View more

Thanks for the link! We had read documentation about shared update groups but just assumed that, since there was an option to open the survey in Survey123 Connect, the capability was there. Perhaps this is an example of the Spinal Tap Exception: just because there's a door doesn't mean there's a stage. ... View more

This functionality is broken for me.  The  link is in a dashboard going to an ID anchor tag in a Hub page.  The correct page opens, but does not jump down to the correct section. Any timeline on this getting fixed? ... View more