Latest Contributions by SFM_TravisBott

Posting to see if a workflow is possible, or if any out there have made it work: I want to ensure that my survey prevents repeat submissions of a particular attribute. An example would be an email - if somebody enters their email and they've already submitted that email, it could produce a warning saying "You've already submitted. Try a different email." and prevent submission. In my case I will have a drop-down list of groups (say Group 1, Group 2.....Group 10). And I only want to accept one survey from each group. So if Group 1 is chosen in the drop-down, but has already been chosen, I want a warning to pop up and prevent submission.  Poking around it looks like the search() appearance could be used to make this happen: specify the URL of the feature service, the field that contains the group information, and, likely incorporating a hidden field not in the feature service, constrain entries to 'if group is found in list of groups, deny submission.' Anybody out there done this? Are there pre-established workflows? ... View more

Having a problem that should be simple but can't quite figure out what is going on.  I am trying to concatenate three text fields into a fourth text field (Field1, Field2, Field3, landingField). One of the fields (Field3) is quite long and somehow is not willing to be concatenated with anything else. It can be calculated over (e.g. landingField = !Field3!) just fine, but it doesn't want to cooperate with anything else.  For instance !Field1' + ' filler text ' + !Field3! does nothing. It doesn't throw an error...just nothing happens. However, !Field1! + ' filler text ' + !Field2! + ' more filler text.' works just fine. I suspected the length of the field was the issue (Field3 is  2000 characters) but I upped landingField to 10,000 characters and same issue. And trying to adjust Field3 by using the .str() method or something similar doesn't seem to work.  Any hints as to what gives? ... View more

Howdy, @Anonymous User , or anybody else that can help.  I am producing a feature report and would like to summarize the individual entries in a select_multiple question. Users have the options to select any combination of A, B, C, D. I would like to be able to count across all records how many times each individual answer (A, B, C, or D) appears. The documentation only notes legal WHERE clause, so that if I broke them each out (e.g. where: "field = 'A'") it would only count options where 'A' was the only option chosen (ignoring A,B, or A,B,C, etc). Is there a technique to count every time 'A' is chosen? E.g. in stead of WHERE field = 'A', an equivalent of field LIKE '%A%'? This is possible using feature sets in dashboards to break them out and summarize them individually but it would be really helpful to count them up in a report.  ... View more

I have a feature service with one geometry layer and three related tables. I have created a view layer by joining the parent geometry layer to a 1:1 related table.  I have a survey that updates the related table. This works great, but I have had difficulty with the reporting since I can't seem to access the parent records for elements of the report. So as a workaround I would like to generate the reporting survey directly off the view layer since it contains all the tables.  The problem: the survey looks fine, however when viewing the data on the survey123 website (where the report is generated) the additional fields joined in from the related table do not show up and can't be pulled in from the report. Why are the additional fields missing? Here's a long list of the fields in the view (this is just a few of them):   The additional fields show up automatically when generating the survey, they are in the xls form, and are present in the surveys preview as well as when the preview is shared.   However, when looking on the website the fields are absent and can't be pulled into the report. The list of available fields stops at those contained in the parent layer.    ... View more

The new map viewer seems to like to alter URLs used for URL parameters to launch Survey123. When copying over the URL into a feature service from map viewer classic into the new map viewer it adds an 'amp', inadvertently, which sabotages the URL parameter.  If I copy this perfectly functional URL from map viewer classic... https://survey123.arcgis.com/share/1bb13b70098942a3b67bc34d1f8be54e?field:County={County}&field:City={City}  ...and then re-open the pop-up editor, it will be altered. The only way it seems to get the URL parameter to work is to go to ago-assistant and delete out the extra four characters. This is what it looks like in ago-assistant prior to fixing it... Can anyone explain what gives?   ... View more