Latest Contributions by NickDierks1

In that use case, your initial if/then statement should work just fine (I'm assuming your username is 'Internal'). Why is there anything to overwrite in the textbox? It should start blank, and populate only via the if/then calculation: name relevant calculation Name property('username') Call_In_Name ${Name}='Internal' [Textbox] if(${Name}='Internal', ${Call_In_Name}, ${Name}) Are you trying to recalculate ${Name}, or do you have something set up in the default column for the textbox question? Are you able to share your csv file? Incidentally, you could also use the coalesce() function and get rid of the ${Name} line: name relevant calculation Call_In_Name property('username')='Internal' [Textbox] coalesce(${Call_In_Name}, property('username')) This will always input the AGOL username unless there's an answer selected in ${Call_In_Name}. ... View more

So if I understand correctly, it sounds like you have two conditions to trigger ${Call_In_Name} being used in the textbox: When ${Name}='Internal' When an option in ${Call_In_Name} is selected For the second condition, you state "if the username is already in there and the user clicks on the select one question." Are there any situations where ${Call_In_Name} is selected, but you still want to use ${Name} instead? If not, then this should probably do what you need: if(string-length(${Call_In_Name})>0, ${Call_In_Name}, ${Name}) This checks to see if ${Call_In_Name} has been answered, and if so, grabs that value. If not, ${Name} is used instead. And just in case someone has 'Internal' for ${Name} but tries to skip answering ${Call_In_Name}, you can put this condition in the required column for ${Call_In_Name}: if(${Name}='Internal') (note, conditionally required questions apparently don't work in web forms) With this setup, the textbox will always equal the ${Call_in_Name} as long as that question is answered. If instead you want to use ${Name} all the time unless A) it's 'Internal' or B) the user wants to optionally override it, you'll need to do that with at least another question and some additional statements. ... View more

From the documentation: if(condition, a, b) Where: condition is the statement to be evaluated a is the result if true ${question} b is the result if false (else condition) property('username') The linked page has plenty of functions and operators to help you set up your if condition. If you're still stuck, describe exactly what you're trying to check and how, and someone can try to help you further. ... View more

Open the "Symbol Layer Drawing" tab in the Symbology pane: From here, it works basically just like it does in ArcMap. Click and drag to easily change the order the symbols are drawn in. ... View more

I'm not sure how you could do that with a single question like that. You could try it as three similar select_one questions: use the same choice list, with the labels/hint text explaining "Pick the 2nd most important issue" etc. Then use constraints like not(selected(${Question2}, ${Question1})) and not(selected(${Question2}, ${Question3})) to keep the user from selecting the same answer each time. Alternatively, you could have seven integer questions (one question for each issue), prompting the user to input a value of 1 through 3 next to different questions to rank them. This would require more work to control, but is still doable. Use similar constraints as above to avoid repeat values (this will be longer because you're comparing to six other questions), as well as adding and .>0 and .<4 to the constraint to keep the range between 1 and 3. Then a final calculation question that calculates the sum of the seven questions and ensures it equals 5, to make sure the user didn't rank less than three issues. It kinda depends on how you want to use the data in your database or reports, and what would make the most sense for the user filling out the form. ... View more

Just wanted to add that the current "fix" still doesn't help matters much at all. I regularly go through several situations where it's incredibly helpful to be able to see the full records as they scroll by: If I need to see the values in a different column than the one being displayed, or looking for values in multiple columns at once. If I'm looking for 'blocks' of similar data that's been sorted together, instead of one record at a time. If I'm looking for highlighted records. Sure, I can toggle the "View highlighted records" button, but if I need to see those in context alongside the un-highlighted records, that doesn't help--I still have to go back and scroll down to them. If I'm quickly scanning the data as I scroll to look for anomalies, particularly in fields that aren't easily controlled by domains or other rules but are still mostly standardized. This goes double if I don't know what the anomalies are, so I can't simply run a search for them. And all of this is not to mention that this fix still causes me to pause the scrolling in order to see anything anyway. I didn't use Pro a whole lot before version 2.0 was implemented, so I don't know what the performance issues were, but maybe give us the ability to toggle this "Scanning" behaviour on and off? Those who definitely notice a performance hit and don't mind the new functionality can leave it on, but those of us who'd rather make it easier to quickly scan and find records can turn it off. ... View more

This seems to work as stated in Connect, but not when published as a web form. The question stays required, regardless of any other conditions in the survey. ... View more

That seems to work just fine. Did you do anything differently? This is how my question is set up: type name label hint constraint constraint_message required date Deadline Due Date Select a due date for completing the map. .>=today() Please select a due date of today or later. yes ... View more

There's actually a way to make this possible, but it involves a lot of setup, and gets exponentially unreasonable with the more choices you have per question. If your survey is relatively short, and your questions ideally have only three possible answers each, then this is likely doable. It all depends on how much work you want to put in to randomize the choices. First, figure out how many permutations there are for your choices. If your questions each have three possible choices (abc), then you have 6 possible permutations (abc, acb, bac, bca, cba, cab). If you have four possible choices (abcd), then you jump up to 24 possible permutations. For each question you want to randomize the choices for, include a different choice list for each of the possible permutations. You'll then include in your form a different variation of each question (each pointing to one of the different choice lists). Then (again, for each question) you can use a calculation with the random() function to generate a random number. Each of your question variants will have a relevant clause set up for one of the possible random numbers generated. Finally, a hidden field for each question will use a nested if/then calculation to collect the response from whichever variant was answered. Don't forget to mark all the question variants as null! This way, your schema will only include one field for each question. Setting up an array of random questions is pretty similar. Again, use the random() function to generate a random number, and use relevant clauses to have one out of X questions randomly appear. Since you're asking for a single questions asked three different ways, you can again collate these questions into a hidden field so that users' responses are spread out between multiple fields in the schema. I've attached an example form that shows this in action. It includes one question with randomized answers (four choices, so 24 permutations), and one randomized question. ... View more

I believe pulldata() should be all lowercase, and there shouldn't be a space in between it and the parentheses. Does your form work after making those changes? ... View more

Dates and Time in Survey123 This blog post is a very helpful breakdown on how to capture, format, and calculate date and time data. If you need help applying that information to your survey, try describing your use case in more detail so that someone can better help you. ... View more

Instead of having the two questions try to populate eachother, make them both null and have them both populate a separate pair of read-only fields. I've attached a sample form that expands on an earlier example I provided on this exact workflow here. The gist of it is that you have your two select_one questions (${SciName} and ${ComName}) and then two read-only text fields with the following calculations: Scientific Name: coalesce(${SciName},pulldata('SpeciesNames', 'SciNam', 'ComNam', ${ComName})) Common Name: coalesce(${ComName},pulldata('SpeciesNames', 'ComNam', 'SciNam', ${SciName})) This does present the possibility of a user selecting both a scientific name and a common name and populating these fields with a mismatch. For that case, we add a constraint to either one of the text fields: if((${SciName}!='' and ${ComName}!=''), (${SciName}=pulldata('SpeciesNames', 'SciNam', 'ComNam', ${ComName}) and ${ComName}=pulldata('SpeciesNames', 'ComNam', 'SciNam', ${SciName})),1=1) This checks to see if both of your select_one questions are answered, and if yes, it makes sure everything matches correctly (the selected scientific name equals the pulldata from the common name, and vice versa). The else case, 1=1 (i.e. no real constraint), is triggered only if one, the other, or neither select_one is answered. The attached form also includes a note question with a similar calculation in the relevant column, which warns that there's a name mismatch. Hope this helps! ... View more

It's free--I think all the ArcGIS Solutions are--but it looks like it does require at least a Standard desktop license, so that may or may not be an obstacle for some. ... View more