Latest Contributions by Environnement_1Lausanne

Hi all, I am currently trying to create a feature report template that contains a table with all the entries from a repeat describing geological layers (repeat name blue and questions within repeat green). I would now like to add a variable (${water_level}) from outside of the repeats (recorded after the repeats in my app) in the middle of the table displaying the repeat entries. Largeur de couche Profondeur Niveau d'eau Nature du terrain Coupe technique ${#new_layer}${layer_width} ${layer_bottom} ${water_level} ${description} ${tech_layer}${/} Whenever i try to upload the feature report template i get the following error message: Failed to parse ${water_level}. Field ${water_level} does not exist or cannot be found in current parsing scope. However if i print the variable somewhere outside the table everything's fine. I tried creating a calculate field within the repeat based on the ${water_level} variable outside of the repeat, but as the ${water_level} is only specified after recording several layers in the repeat, the water level value gets only assigned to the calculate field of the last repeat entry.   Does someone have an idea how i could solve this? Cheers, Flo feature report‌ repeat template‌ survey 123 repeat‌ ... View more

Hi all, In my survey123 survey, I have a bunch of grouped questions that appear if a user selects a certain topic in a first question. For my feature report, one group of question translates to a separate table containing the results of all the questions within that group. My question: is it possible to only include grouped questions in a report if the group was activated through a multi_select first question. I would like to avoid having pages of empty tables in my report. Here's an example of what I would like to do: ${if ((categories | selected: "dangerous_substances"))}       Substances et liquides susceptibles de polluer les eaux / sols Note : ${ evaluation_dangerous_substances_liquids | getValue:""} Citernes diesel sur place : ${ diesel_tank | selected : "yes"}   Oui ${if ((diesel_tank | selected: "yes"))}Nombre : ${nb_tank}${/} ${ diesel_tank | selected : "no"}   Non ${if ((diesel_tank | selected: "yes"))}Nom citerne : ${ name_tank }${/}   ${if ((diesel_tank | selected: "yes"))}Date du dernier contrôle : ${ date_last_control }${/} Conformité des citernes : ${ conformity | selected : "yes"}   Oui ${ conformity | selected : "no"} Non Autres substances à risque : ${ other_substances_risk | selected : "yes"} Oui ${ other_substances_risk | selected : "no"} Non ${if ((other_substances_risk | selected: "yes"))}Substances présentes : ${ other_substances}${/} Stockage conforme : ${ storage_compliant | selected : "yes"} Oui ${ storage_compliant | selected : "no"} Non ${if ((storage_compliant | selected: "no"))}Précisions : ${ storage_compliant_details}${/} Remarques : ${ remarks_substances } ${/} So in this example, I would like to only show the table and the referenced values, if that category of "dangerous_substances" was ticked earlier in the survey. Any ideas? feature reports‌survey results‌#report ... View more

Hi, I am running through a problem since the latest releases of survey123 (3.5 and above) with constraints. The issue: After spending a bunch of time in connect trying to find what was wrong with my formulas in the constraint column, I figure out that the validation would occur only when I attempt to submit the form. I first though it was a bug, but it seems that this should be the intended behavior since 3.5 and the introduction of inline validation. I could find a few posts about it, but nothing clearly stated in the official survey123 help: https://community.esri.com/message/863637-what-happened-to-constraints https://community.esri.com/message/882496-grid-meets-read-only-and-constraint https://community.esri.com/message/890114-constraint-not-working https://community.esri.com/thread/205058-survey123-connect-now-constraint-not-working (See Evan's issue of august 19) In the blog posted by Ismael for the 3.5 release, the only statement about it is the following: Constraint and required messages now appear inline, helping you identify the exact questions in your form that need attention. This is particularly useful when you have long forms, or forms with multiple  pages. Why this is an issue: This behavior means that the user can fill the entire form before noticing that a mistake was made. First of all, it is annoying to come back to questions especially when forms are long and users expect to be done with it at the end Calculations can still be made based on the wrong value The user might do (irreversible) mistake on the field before he realizes a wrong value was entered Example: Simple example, not so critical (could be much worse): User needs to indicate the maximal diameter of the components found in the ground (gravel, rocks...) Based on that value, the survey indicates the weight of the sample that needs to be taken The user made a mistake with units (cm instead of mm) and the survey indicates to take a sample of 5kg instead of 30kg The user proceeds, and continue the form while the sample is sent to laboratories... Possible workarounds: I can imagine several workarounds, but nothing is worth the original constraint behavior that was before 3.5. Moreover, it means that all the existing surveys need to be updated in order to prevent users from doing mistakes. Use the inputMask column: very limited (cannot use regex, compare numbers (<>), use other fields or many other usefuls fonctions as the one shown here) Use an additional field that will show up when the constraint is no met (cumbersome, user can still ignore or miss the message, issues with layout in grid-theme) Use bind:esri:warning column (still, it is only a warning, not sure if all function listed in 1 would work) Questions: Firstly I hope first that I didn't miss anything, and this is the actual intended behavior and not a bug. If so, I would like to say that the inline message is great, clearer that before. The only issue is the moment when the validation takes place. Is it possible to do the validation while the user is filling the field (as for the input mask column) and not once the user attempts to send the survey? Do you have any other workaround that would get closer to the original constraint behavior? Thank you for your time and your help. Léo ... View more

Hello,   It would be very useful to be able to very simply identify which features have attachments. It could be a column in the attribute table with a boolean TRUE / FALSE value for the ATTACHMENT field. Even better, an additional column saying how many attachments are linked to each features. Thanks in advance ... View more

Hello, As more and more users use surveys in our company, the Survey123 mobile gets incredibly crowded with surveys when we click on "Download surveys". Would it be possible to rearrange surveys in folders ? For example, first level : member name Second level : folder created by a member for a given project. The structure would be similar to the one in ArcGIS Online. Is such a feature planned ? If yes, when should it be released ? Thanks ! ... View more