Latest Contributions by JamesTedrick

Hi Vanessa, It sounds like something got stuck during the upload process.  This is often a transient issue; have you tried closing Survey123 Connect, re-opening and attempting to republish? ... View more

Hi Jay, Again apologies for not getting back to this quicker.  I've made some updates to the script (including the manual fixes I applied above).  Can you redownload it and try again? ... View more

Turns out I misspoke a little- the link to launch Navigator can be generated by Survey123, it's just the validation is a bit strict.  Find below a sample that does so. ... View more

Hi Weng, Yes, you're right about the discrepancy in values in the client application and what the feature service endpoint can accept.  In response to your question and my response, I entered an issue into our development team to fix this behavior- we'll have it updated to submit null (but still use NaN in the app) in the next version. ... View more

Hi Susan, How are you originally opening Navigator?  Currently, there isn't a built-in relationship like there is between Collector and Navigator (we rely on Workforce or another similar system to manage that). It might be possible to create an app link url, using the callback url (as defined towards the bottom of the README at GitHub - Esri/navigator-integration: Multi Language repository that contains documentation and sample code for creating … ) to launch Navigator with a 'return to Survey123' link (using it's app schema url, arcgis-survey123://itemID=... , detailed at https://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-scheme ).  The starting point would need to be a html page or something producing HTML output (a pop-up, for example, could do this in Explorer); currently we can't construct that complex HTML in Survey123 on the fly (and thus start with Survey123. (see reply below). Can I ask about how you're wanting to use Navigator & Survey123 together, and what obstacles using Workforce as the intermediary currently present? ... View more

Hi Peter, Thanks for pointing out the need to check the survey compatibility.  Implementing this well is a bit difficult as we can't guarantee the the ability to validate that the survey still matches *before* collection,- collection may happen offline or the network environment may end up being slow enough to significantly hold up collection.  If we check after collection but before publishing, it's still the same situation as you are experiencing, perhaps with a better error message; there's no way to automatically convert between an old form and a new form (we could make assumptions about field names, etc, but that would be a bit risky). As for reading the data from old forms, we can provide a bit more help.  The fist step is to extract the survey (an attachments); refer to Troubleshoot—Survey123 for ArcGIS | ArcGIS for guidance.  I've posted a script at GitHub - tedrick/ReadS123DB: Convert the survey data stored in the Survey123 Field App into a set of CSV files  that will read the database that stores all submissions on the device and export them as a series of CSV files.  From there, you can process the information like any other dataset. ... View more

Hi Weng, I think what you're thinking of in terms of integers field input is null, which is a valid input value; NaN isn't.  There's a slight difference between NaN and null programmatically; while they represent the same concept, they are not equivalent. ... View more

The function is uuid() .  Note that if you want to create a GUID field (the default is text), you also need to set the bind::esri:fieldType column for it to esriFieldTypeGUID.  See the attached file. ... View more

Carmel is correct- cascading selects are an in-program filtering and aren't represented via subtypes in the Feature Service (that would limit some of the complexity that can be done with cascades). ... View more

Hi Loretta, It's a little hard to debug with just the error you provided; given the line number, it's the statement: outRow = jRow["attributes"] If that's the case, it sounds like the the previous line has not created an object from the data part of the row stored as a string.  Line 19 should be          jRow = json.loads(json.loads(row[1])) you might try wrapping another json.loads() around.  One way to find if you're on the right track is to do a print jRow statement and observe what it looks like   Below are examples of what the print statement returns as the program converts the data into into an object; it needs to look like the last one : row[1]: "{\"attributes\":{\"note1\":\"6\",\"stationid\":\"31003\",\"numbikes\":\"6\",\"bikesreported\":5,\"numbroken\":3},\"geometry\":{\"spatialReference\":{\"wkid\":4326},\"x\":-77.049593,\"y\":38.86017,\"z\":null}}" ----------------- json.loads(row[1]): {"attributes":{"note1":"6","stationid":"31003","numbikes":"6","bikesreported":5,"numbroken":3},"geometry":{"spatialReference":{"wkid":4326},"x":-77.049593,"y":38.86017,"z":null}} ----------------- json.loads(json.loads(row[1])): {u'geometry': {u'y': 38.86017, u'x': -77.049593, u'z': None, u'spatialReference': {u'wkid': 4326}}, u'attributes': {u'note1': u'6', u'stationid': u'31003', u'numbroken': 3, u'bikesreported': 5, u'numbikes': u'6'}} If you further assistance debugging, I'd suggest opening a technical support case- it would be a bit easier than to debug remotely via GeoNet. ... View more

Hi Francisco, What you're experiencing is an interplay between default and relevancy.  As you might expect, a default value is only assigned when the form is created.  When a question goes from relevant to not relevant (i.e., not displayed), the answer for that question is removed; this is to ensure we don't save answers to questions that, according to the form's logic, haven't been asked.   As a workaround, instead of supplying a default value, we can use a calculation that uses the same statement as your relevant clause in an if statement to calculate in the default value - see attached. ... View more

Can you share the XLS file?  I'm also wondering a bit on the survey design - you have separate sets of questions based on the size of the TV - are they the same questions (for different sizes) or different questions per size? ... View more

Hi Jay, Apologies for being less responsive - I've been tied down with other tasks.  I'm going to do some testing with the script  and get back to you on this tomorrow. ... View more

As it turns out, that part is already in the code, just set up for repeats, not parent forms.  Around line 243 of the python file, there is: if 'parentrowid' in originFieldNames and 'rowid' not in originFieldNames: Change that to: if 'rowid' not in originFieldNames: ... View more