Latest Contributions by CarlBeyerhelm1

‎08-20-2023

OK. Thanks for the follow-up. Good to know.

‎08-20-2023

Thanks for your reply. Yes, I configured the map symbology colors in the "new" map viewer...not in Classic. Then, when I created the QC project, the buttons automatically inherited their color from the map symbols for each of the six map classes, and I assumed that QC's lines would inherit matching colors too, but they didn't. I'll try again to see if I can find where things went off the rails.

‎08-18-2023

I'm a total QuickCapture rookie, so I'm probably missing something basic. I established symbology and color for my underlying QC layer, but when I am capturing data the buttons are the correct color, but the lines in the map view do not match the button color. See the attached screenshot. What am I missing? Thanks!

‎03-08-2023

Hi Zach. Yes, within the survey itself. For instance, when a record is retrieved for edit from the Inbox, I want to be able to make some questions read-only if the current logged-in username is not the same as the original CREATOR. Essentially, this is setting up dynamic read-only questions dependent on the original CREATOR (posted the original record to AGOL), and the current editor. Thank you.

‎03-08-2023

I would like to access fields that are in a survey's underlying feature service, but are not in the survey. For instance, get a value from the editor tracking fields CREATOR or EDITOR for the current record from the survey's underlying feature service. Is this possible?

‎02-06-2023

No worries, Doug. It's comforting, I suppose, that other people have hit the same hurdle...so it's not "just me"! ;>)

‎02-06-2023

Yeah, I looked around quite a bit, but couldn't seem to find much guidance on best practices, or issues, in double repeats. In my case, the OBSERVATIONS table is parent to the OBS_POINT, OBS_LINE, and OBS_POLY repeats, as well as the INDIVIDUALS repeats, so it is a bit convoluted. Anyway, I incrementally tested each parameter in the OBSERVATIONS repeat, and discovered that OBS_POINT, OBS_LINE, and OBS_POLY data can successfully be retrieved to the Inbox if I remove the value of 1 from their repeat_count parameter. I had wanted only one spatial feature to be recorded for each observation. The cause-and-effect between a repeat_count limitation and failure to retrieve Inbox data is a mystery to me…as are many things. HA! By removing the repeat_count limitation, however, I had to add a constraint parameter like count(${OBS_POINT})=1 or NULL to avoid exceeding 1 feature per observation. It does the trick, but you actually have to create/accept the second feature before the constraint kicks in, at which point you have to delete the second feature...which is kind of clunky. So, I'll put this fix in the category of a work-around, but not a clean solution. Thanks for weighing in.

‎02-06-2023

Thanks for your reply, Doug. Unfortunately, removing underscores from the 3 OBS feature layer names was not a remedy. Plus, the SITE_POINT, SITE_LINE, and SITE_POLY feature layers higher up in the schema contain underscores, and they are successfully returning data to the Inbox. I don't know if it is related or not, but there is something funky going on in the OBSERVATIONS and INDIVIDUALS repeats, because default values that I've set do not appear in the first record of a repeat, but do appear in subsequent records of the repeat. It has me stumped...

‎02-03-2023

My survey has a somewhat complicated data model, as illustrated below. Each of the 9 nested repeat elements are made relevant by choices made in the the repeat's parent. When I open a survey from the Inbox, all of the nested repeat data are present, except for the OBS_POINT, OBS_LINE, and OBS_POLY layers. Each of the repeats includes a value of "query" in the begin repeat question's bind::esri:parameters parameter. The OBS_POINT, OBS_LINE, and OBS_POLY data do appear in the corresponding hosted feature layers, so I know that data capture and sync have been successful, but Inbox data retrieval for the OBS_POINT, OBS_LINE, and OBS_POLY layers was not. The survey's XLSX is attached. Any insights would be appreciated. Thank you. Data retrieval via the INBOX was successful for yellow-tinted elements, and failed for the blue-tinted elements.

‎02-03-2023

Is it possible to have grid cell widths set dynamically within the appearance column of Survey123 Connect? For instance, instead of having an explicitly defined grid appearance such as w4 multiline predictivetext, I was hoping for something like w${calc_width} multiline predictivetext, where ${calc_width} is the result of a calculation based on other questions. I can't seem to find guidance on this, and attempts like that above have not been successful. Thank you.

‎02-01-2023

OK, thank you. Does the functionality work for geotrace and geoshape questions too?

‎02-01-2023

I created a GPS quality threshold by placing a numeric value in the body::accuracyThreshold parameter of Survey123 Connect, and it is working as expected. What is not working is the ability for users to manually override that quality threshold as described in this blog post. https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-xlsforms-and/ba-p/894139 There is no spinning location icon, and touching other items in the widget doesn't commence GPS logging. Is that functionality no longer supported, or did I miss an important step somewhere? Thank you. - - - - - - - - I can't seem to override a GPS threshold as was illustrated in this blog post.

‎04-30-2018

For info... I'm in Windows 10 now (was in Win7 previously), and arcpy.TestSchemaLock() now seems to be working in 10.5.1.

‎12-12-2017

OK, thanks. I guess the workaround is to bracket schema lock-prone code with try: and except:

‎12-11-2017

Thanks. Could you re-try posting your link, please? I'm getting a "This bug does not exist" page.

Online Status	Offline
Date Last Visited	‎09-11-2023 08:56 AM

My Ideas

Latest Contributions by CarlBeyerhelm1

Re: QC line colors in map view do not match the button colors

Re: QC line colors in map view do not match the button colors

QC line colors in map view do not match the button colors

Re: Access fields that are in a survey's underlying feature service, but are not in the survey

Access fields that are in a survey's underlying feature service, but are not in the survey

Re: Inbox data retrieval fails for some nested repeats, but not all

Re: Inbox data retrieval fails for some nested repeats, but not all

Re: Inbox data retrieval fails for some nested repeats, but not all

Inbox data retrieval fails for some nested repeats, but not all

Dynamically change question width in a grid

Re: Can't manually override GPS quality threshold.

Can't manually override GPS quality threshold.

Re: arcpy.TestSchemaLock misbehaving at 10.5.1?

Re: arcpy.TestSchemaLock misbehaving at 10.5.1?

Re: arcpy.TestSchemaLock misbehaving at 10.5.1?

Re: Inbox data retrieval fails for some nested rep...

Re: Inbox data retrieval fails for some nested rep...