Latest Contributions by Jim-Moore

‎01-16-2019

Hi Jeff, glad you found the info helpful. Regarding barcodes, as long as the string returned from the barcode matches an old meter number in your CSV it should initiate the pulldata on the other fields. Add a barcode question specifically for old meter number barcodes; then add a calculation on the old meter number question to read in the string from this barcode question. If the string returned from the barcode includes extraneous information, you can use the method described here by Philip Wilson to extract the relevant part from string. Jim

‎01-15-2019

Thanks Matt, I'll pass this on to our team and get back to you with any developments.

‎01-13-2019

Hi Jeff Thanks for providing the XLSForm. One suggestion would be to add a select_one that prompts the user to specify if they have the old meter number OR the address. Based on the response, the user is prompted to enter the known value into another question (using relevant to present the applicable question). Then use an if statement to calculate oldmeternum: if user enters an old meter number, use this value; otherwise use pulldata to look up the meter number using the entered address. Your existing pulldata calculations should then work as normal. Please see an example attached. If you do not wish to store these additional questions as fields in the feature service, use the 'null' option in the bind::esri:fieldType column. This assumes one address has only one meter, and vice versa. The pulldata function is essentially a text lookup, so the user would have to enter the address or old meter number exactly as it appears in the CSV for it to get a match. One way to ensure the old meter number or address is entered correctly would be to use select_one for these questions using the 'autocomplete' appearance so the user can filter/select from a drop-down list. The values would have to be added to the choices tab; if you have a very long list of addresses/meter numbers this might not be practical and may affect performance, in which case an external select might be useful (see Cascading and external selects—Survey123 for ArcGIS | ArcGIS for more info). Jim

‎01-13-2019

Hi Matt This issue has been raised previously and our team is looking into a resolution. We will update this thread when we have more information. In the meantime... 1) Could you please let me know what version of Portal you are using? 2) Other users have encountered some similar issues where the required capabilities of the feature service/layer in Portal are not enabled. Can you confirm if the following are enabled: supportsApplyEditsWithGlobalIds =true Create,Delete,Query,Update,Editing,Extract,Sync capabilities Thanks, Jim

‎01-09-2019

Hi Pamela Another option would be to apply a constraint to the select_multiple, to check if more than one answer is selected when NA is selected. For example: if(selected(${question}, 'NA') and count-selected(${question}) > 1, false(), true() )‍ You could then add a constraint message to explain that no other selections are allowed when NA is selected.

‎12-26-2018

Hi Pamela There isn't a way to do this with a select_multiple question; all responses to a select_multiple are stored together in a comma-separated string. In your survey, would it be feasible to include a question preceding the select_multiple (e.g. "Is there a previous value?" Yes/No) that controls whether the user sees the select_multiple (using the relevant column) and/or sets a default for the select_multiple? Some handy general info here: https://community.esri.com/groups/survey123/blog/2017/08/30/understanding-multiple-choice-questions-in-survey123-for-arcgis Jim

‎12-19-2018

Hi Adam Apologies, I misread your workflow; the thinking was the if statement could be used to set a default for a new asset, i.e. one that doesn't have an existing asset_tag and isn't already in the CSV. I now appreciate this isn't particularly useful in this survey! Regarding this workaround... The work around is to use 2 fields, 1 text field "kickplate1" using pulldata, and 1 select_one field "kickplate2", only relevant and with default values if "kickplate1" is null. The obvious problem here is having to create 2 fields for capturing each attribute. ...to assist with this, you could use a calculate question with a null field type (as I see you've already used for several other questions). This would omit the question from the feature service, so you're not storing superfluous data. As you've suggested, put a pulldata in the calculate question. Then use an if statement for the select_one, e.g. if(${calc_kickplate}='','Small',${calc_kickplate}). Providing the values in the CSV exactly match the choices for the corresponding select_one, the correct value will be selected in the form. The user can then modify this selection if required. Alternatively, would it be feasible to add the default values into the CSV, for all door records that have empty values? Then you could use the pulldata on its own.

‎12-16-2018

Hi Adam Just confirming: a default is applied when the survey form first loads or, if in a repeat, when a repeat record is added; a calculation is applied when the values it relies on change. In this case asset_tag is calculated, which in turn applies the calculations for vision_light, kickplate, etc. (overwriting their defaults). One suggestion would be to modify each calculation so that it results in a default value if the asset_tag is null. For example: if(${asset_tag}='','Small',pulldata('features','kick_plate', 'asset_tag', ${asset_tag})) Setting a default for 'thickness' in the default column should work as normal as this question does not have a calculation. Jim

‎12-13-2018

Hi Adam, thanks very much for the XLSForm and other survey files. At a quick glance it looks like the pulldata calculation could be superseding the default. I'll take a look and report back. Jim

‎12-12-2018

Hi Bonnie, it isn't possible to hide a question after it has been answered (while retaining its response), but hopefully my reply to your related post provides some useful suggestions. Jim

‎12-12-2018

Hi Naomi, just adding a note from our discussion for the benefit of the forum... The text was not visible in the attribute table in Naomi's web application because the domain was not updated in the feature service following revisions to the choices list for a select_one in the survey. Naomi solved this by manually updating the domain on the feature service. For a select_one question in Survey123 the domain is created when the survey is first published, however the domain is not updated on subsequent modifications to the choices in the survey. Options are to manually add the domains to the existing feature service or publish the survey again from scratch to create a brand new feature service. This issue has been raised as an enhancement. I'll add this post to our internal enhancement request and update this thread if/when info becomes available.

‎12-12-2018

Hi Bonnie, thanks very much for the XLSForm. Regarding (1) in your original post, this is related to an issue that we're aiming to have fixed in the 3.2 release. An update will soon be available on EAC for testing. Regarding (2) you're right: responses are not stored for questions that are not relevant, so when switching between the 'device' and 'standalone' options any entered data will be lost. One way to work around this would be to simplify the form so that it uses one repeat for photos, instead of two. Please see Example1 attached. In this example, all records (regardless of whether they're 'device' or 'standalone') are recorded in the same table; for each record, the user specifies if the photo was taken with the device or standalone camera. Alternatively, if you require the data to be stored in two separate tables (one for 'device' and another for 'standalone', as per your original design) you could keep the two repeats separate (something like Example2, attached). Jim

‎12-11-2018

Hi Dudley, thanks for the XLSForm. I am unable to reproduce the issue. The relevant questions work as expected when I open your survey on Android (see attached). Which version of the Survey123 app are you using? And on which Android device (make, model and Android version)? Just to clarify, for select_one questions ${GotHabitat}='YES' is correct, although selected() will also work. I thought it might be worth trying the selected() option but my apologies, it was a bit of a red herring! So ${DateSeasonChoice} != 'UNKN' is correct for specifying 'not equal to' on a select_one. Jim

‎12-11-2018

Hi Naomi, that would be great - my ArcGIS Online username is jmoore_survey123. Feel free to send me the web app link by direct message if you prefer.

‎12-11-2018

Hi Erik, that's correct, your description is spot on. It could be that you allow your field staff to open both surveys in the Survey123 app. They could use the original survey to submit new records only (disable the inbox on this one so existing records cannot be modified) and then switch to the new survey (with inbox enabled and some fields set to read-only) to make edits to existing records. Alternatively, if field staff do not need to use the original survey you could simply stop sharing it with them. Jim

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by Jim-Moore

Re: Survey123 Connect PullData Compound Question

Re: Cannot upload attachments

Re: Survey123 Connect PullData Compound Question

Re: Cannot upload attachments

Re: Another value ( NA) in Select Multiple option

Re: Another value ( NA) in Select Multiple option

Re: Default value for a select_one question type

Re: Default value for a select_one question type

Re: Default value for a select_one question type

Re: Is it possible to hide the question after it is answered?

Re: Missing text in web app attribute table

Re: Entry getting reset on switching visibility based on relevant value

Re: Survey123 Form on Android doesn't open "relavant" Groups

Re: Missing text in web app attribute table

Re: allowUpdates for specific questions

Re: Calculating Hours between two Time questions

Re: Survey123 videos on mediaspace site presenting...

Re: Select_Multiple conditions

Re: Survey123 Report Template Error

Re: Multiple-page Survey123 form