Character Mask causing issues on other user entry fields

MeganEngel — Mon, 08 Feb 2021 20:28:23 GMT

Hey all,

My end users have been encountering a strange glitch in some of the QuickCapture applications I have deployed.

Background:

One feature layer where there is a details attribute field, that is populated either through character masking or free text depending on the point type.
Some point types require a specific character mask (i.e. "WA-102" for wetland A, flag number 102).
When the user selects a point that has a user entry with free text, not a character mask, the character mask for wetlands populates and the user can only enter data in that format.
Work around: the user collected that data point, closes out the specific QC app, then re-opens the app and the point then allows the user to enter free text.
- Once the app is closed and re-opened, that glitch doesn't occur again

Have other uses been encountering this problem? What sort of workaround do I need to do on the author side of things, so I can make sure my end-users don't have to deal with this weird work around in the field. They know what they have to do, but it is annoying for them.

Re: Character Mask causing issues on other user entry fields

JohnathanHasthorpe — Tue, 09 Feb 2021 12:58:59 GMT

Hi Megan - I'll try to replicate this issue for you.

Re: Character Mask causing issues on other user entry fields

JohnathanHasthorpe — Thu, 11 Feb 2021 11:58:49 GMT

Hi Megan, I can replicate this bug and we will get it fixed in the next release of the app.

Version 1.10 due out post Dev Summit.

Re: Character Mask causing issues on other user entry fields

MeganEngel — Thu, 11 Feb 2021 15:46:48 GMT

Thank you for looking into that John!

topic Re: Character Mask causing issues on other user entry fields in ArcGIS QuickCapture Questions

Character Mask causing issues on other user entry fields

Re: Character Mask causing issues on other user entry fields

Re: Character Mask causing issues on other user entry fields

Re: Character Mask causing issues on other user entry fields