Latest Contributions by IsmaelChivite

‎10-17-2016

Ah. I see. Looking closer into your URL in the Custom Attribute Display I noticed that you are separating the parameters using a semicolon instead of using an ampersand (&). Can you please try fixing that? Try something like: <a href='arcgis-survey123://?itemID=484c436819d7469aa62b2904452771cb&field:facilityID={facilityID}'>Hydrant Form</a>

‎10-17-2016

Hi. I am not sure I follow here. Your screenshots indicate that the only attribute from your Hydrant layer that you are passing to Survey123 is the FacilityID. I would not expect any other attribute to be passed (in your Desktop or Phone).

‎10-14-2016

Hi Dan. We want to support default values within repeats in our 1.9 release, which is tentatively scheduled for late October 2016. The fix is being tested at the moment. If we feel it is a solid fix, will ship with 1.9.

‎10-12-2016

Hi Bob. This is an interesting use case. We had not run into this one before. The reason why you are getting the error is that Connect is trying to add to geometry fields into the feature layer and this is not supported in the ArcGIS data model. Once you add a geopoint question, you can't add any more geometry fields within that layer. I guess it would be handy in this case to have an appearance that would allow you hide the geopoint question, but at this point we do not have it. I would suggest that you for now put the geopoint at the end and you calculate the location as you are currently doing. Try making the geopoint question read-only so the user cannot overwrite the location you assign. As for the hidden question, you can either remove it, or if you prefer you can add two hidden questions where you can store the X and Y coordinates separately (as the result of your calculation).

‎10-11-2016

Hi Hector. I had a look at your survey. Here are some notes: The reason why Survey123 does not let you submit values is because you are combining an input mask with a decimal type of question. Your input mask is by default creating a value which is not a valid decimal number. Unless the user types a proper decimal value, Survey123 will complain. I suggest that you change the question type to text to avoid the above behavior. If you want your pH values to be stored as a number in the geodatabase, then use the bind::esri:fieldType column to set the target esri field to be esriFieldTypeDouble There are two more issues with this survey: Some values in the NAME column of the Survey worksheet are highlighted in red. This is because they are repeated. Values in the Name column must be unique. In the choices worksheet, you also have values in the Name column that are invalid. Values in this column must not contain spaces or include non-ascii characters. I am attaching a modified version of your survey for you to try. An alternative approach for pH values may be to make the question types decimal, remove the input mask and add a constraint that will ensure values are within 0 and 14. Hope this helps.

‎10-10-2016

The expected behavior is that an input mask filters the user input to prevent the user from typing an entry that does not conform with your mask. Input masks should not however prevent you from submitting the survey. For example, if your input mask is B9.99 but you do not flag your question as required, you are expected to be able to submit the survey even if you leave the answer empty. It may be best if you share your survey (attaching the survey to a comment in this thread using the advanced editor) so we can have a closer look at your problem. Please also let us know what is the version of Survey123 you are using.

‎10-07-2016

Hi. I hate it when computers take things so literally. Change the the parameter name to itemID and you will have a better chance. The parameter is called itemID, not ID. This link should work for you: arcgis-survey123://?itemID=44fd0897c4f741f3adc8ad6e824d0fbf In my case, the link does not work (see screenshot below) because my user does not have access to your form, but for you it should work.

‎10-05-2016

Hi. This issue has been addressed. You can now use today() in Survey123 questions of type Date, and now() in Survey123 questions of time DateTime and Time. Thanks!

‎10-05-2016

Would you be willing to store the date in a separate question, for example using a Calculate type of question? That is: you would keep your Date type of question (would be stored as an esriFieldTypeDate) and add an additional question of type calculate which would be stored as an esriFieldTypeString. If you would not mind this solution, we could help by providing you with the means to format date objects into the string question (the calculate). At this moment in time we do not support the format-date(date, format) operation but we could consider adding this operation if you think the solution described above would work for you.

‎10-05-2016

Hi Geoff. Can you please share your XLSFile?

‎10-04-2016

Hi. I just got word from the Collector for ArcGIS team. This is an issue specific to iOS10. The team looking at tentatively addressing this in the next update to Collector for ArcGIS. Collector iOS (issue limited to iOS10): BUG-000099603. Collector Android: BUG-000088624.

‎09-30-2016

Hi. Unfortunately not out of the box. You cannot dynamically get the X,Y coordinates of a point feature from your popup. However, you could get the X,Y coordinates from a feature using the ArcGIS API for Javascript, Python or something similar. If you provide some more details on the particulars of your workflow, we may come up with a workable solution.

‎09-29-2016

Thanks. We will need to look into this one. I just wanted to state that Survey123 at this moment will enforce your constraints even if the question is left with no answer. There is nothing wrong with your survey. Logically, we would want to ignore constraints in non-required questions that are left empty. We will look into this and see if we can resolve in a future update. In the meantime, I strongly recommend that you open a Tech Support incident referencing this thread.

‎09-29-2016

Attaching slightly modified XLS file. Tested on 1.8. I hope it works for you.

‎09-29-2016

Hi! I think I found the problem: If you remove the relevant expression in rows 9 to 18 (included) your form looks to behave as you would expect. I used 1.8 to perform this test. So here are some notes on what is going on. You have a begin group statement in row 8. You are applying a relevant expression to this group. This is great, because applying an expression to a group, will hide or show all questions within that group accordingly. The issue seems to be that you are ALSO adding the same expression to every question within the Group. These redundant relevant statements are making the defaults not to show up.

Online Status	Offline
Date Last Visited	‎07-10-2026 08:41 AM

My Ideas

Latest Contributions by IsmaelChivite

Re: Automatic transfer of attribute to Survey123 from Collector not working

Re: Automatic transfer of attribute to Survey123 from Collector not working

Re: Default values and calculations not working in Repeat

Re: Hiding a geopoint populated via pulldata

Re: Using a Mask makes the input required even when the atribute is not visible?

Re: Using a Mask makes the input required even when the atribute is not visible?

Re: Understanding Survey123's custom URL Scheme

Re: Recording current time in Survey123

Re: Formatting date in Survey123

Re: Inventor's Day Release (1.8)

Re: Survey123 Not Opening From Collector Link

Re: Understanding Survey123's custom URL Scheme

Re: Constraints Still Apply For Empty Non-Required Fields

Re: Why is date constraint not working?

Re: Default values not populating when there is a relevant expresson

Re: Auto complete function for multi select questi...

Re: Survey123 Inbox not returning repeat data

Re: Creating a unique ID in the Survey123 web desi...

Re: How to add two or more relevant to select_mult...

Re: Is it possible to allow users to edit records ...

Wildfire Response GIS