Latest Contributions by JamesTedrick

Hi Kevin, Survey123 caches your login information so that it can be preserved when you go offline; it may be that while it appears you're signed in, the login token expired and was not renewed.  Did this happen after a period of time either disconnected or not using the application? ... View more

Thanks for the catch- I'll add a Delete statement to clear up the stat tables (all other points where I create an in_memory table I already had it clean up at end). ... View more

Hi Bret, This sounds like two separate issues.  The difference in publishing with Survey123Connect vs. the website should not affect the ability to migrate the survey.  During the migration script, are there any messages that appear that might indicate something is amiss?  Another common error I found during development was not specifying the correct timezone- in North/South American contexts, it can lead to no rows copying over as the records are from the 'future' (time in UTC vs. local time) and thus after the synchronization time. On the other view/non-view part, with the December release of Survey123, the website now takes advantage of a new feature in ArcGIS Online - the ability to create 'Feature Service Views'.   ... View more

Yes, it should be detecting the existing tables (there's a function that searches for the tables).  Can you verify that the table names in the database match the names as they appear in the script?  I'm wondering if there might be an issue over schema/username (i.e., GIS.GRSM_SASQUATCH_SRV_EVENT - this should be found by the search pattern) or capitalization (GRSM vs grsm). ... View more

Hi Brent, There isn't a way to have a question 'float' at the top or bottom of the survey. I've logged the idea of a user-supplied help file as a possible enhancement- you might want to go to the ideas.arcgis.com website and log it in there, so other people can provide comments/upvote it (it helps gauge the audience for an enhancement). ... View more

Hi Stacey, Before version 1.10, the parent-repeat relationships were linked using the RowID column.  If your surveys don't have repeats (or, for the purposes of Collector, you're not using the repeats), you can easily hide the RowID field when publishing the service by hiding the RowID field.   With version 1.10, we now support using the GlobalID as the field that the parent-repeat is based off of.  The script still creates a rowID field when there are attachments because the normal behavior of globalIDs is to be auto-generated, not set when copying over data; the script can't copy over the existing globalID info and needs a rowID as a place to store the previous value so that a lookup dictionary can be created.  RowID for used in this case can be hidden afterward as it doesn't participate in the attachment relationship. ... View more

Ah- I missed that this is Connect, not the field app. I assume there are no issues in accessing the ArcGIS Online with the same credentials?  From what you're describing, it does sound like a proxy or other network setting issue.  Could you attempt to create a log file of the login experience (directions at Troubleshoot—Survey123 for ArcGIS | ArcGIS ) or open a technical support request? ... View more

Hi Gary, Yes, this is the current expected behavior for end time with repeats.  Conceptually, end time is more problematic with repeats than the parent form- there's no defining final event with a repeat (as data submission is for the entire form); they can always be revisited/edited before form submission. ... View more

Hi Andrew, There are a couple of situations that can generate the public account error message accidentally.  Can you describe in more detail when this happening - is this in a mixed connected/disconnected environment?   ... View more

Hi Joe, a small clarification - a new group does not create a new table, a new repeat will.  If you take a look at the schema view in Survey123Connect, you shouldn't see any evidence of the group entries- they're a visual/organizational device only. ... View more

Hi Roger, The database created by Survey123 doesn't have a password.  I'll contact you offline to try to help resolve this issue. ... View more

Hi Andreas, In case the above comments didn't resolve the issue (and to also provide documentation for future searches), ArcGIS Online is built on cloud architectures that generally don't rely on static IP addresses; the preferred solution is to whitelist domains.  The list of domains can be found at http://downloads.esri.com/resources/enterprisegis/AGOL_Domain_Requirements.pdf  ; it also provides references to the IP addresses if explicitly required (though you essentially are whitelisting all IPs owned by the cloud providers that ArcGIS Online uses). ... View more

Hi Brent, There are a couple of issues with displaying an instructions page as you describe it- Survey123 isn't an application that internally uses hyperlinks like a web browser (it supports some HTML formatting but isn't HTML itself) and application sandboxing would make it a bit difficult to view the HTML document in a web browser or other application. That being said, a couple of other ideas for providing access to instructions: (Online only) – Create an instruction manual as .doc/.pdf and place it online. Have a hyperlink in a note that links to the document Embed the instructions in the surveys as notes; use a select_multiple question as ‘Show Instructions’ (with a 1-value choice list) and have the instruction notes be relevant on whether the ‘Show Instructions’ question is checked. ... View more

Hi Tucker, In reality, you aren't creating two apps.  You needed to create the first one to test the app before upload, which creates the actual item.  It might be better to start by immediately uploading the application after creation to your account and generate the clientID first thing.  Alternatively, you could simple have 'App1' as a resident testing clientID, reusing the clientID from app to app in development and then updating with the 'App2' clientID for production.  The main benefit of using separate application IDs is better per-app security/sharing and metrics. Normally invalid client_id occurs because of a mismatch between the Portal/AGO that you registered the app and what you're trying to log into.  If you're creating an application that is going to be used across multiple Portal/AGO environments, you'll need to create an item for the application in each environment and then set them to have identical clientIDs.  It's probably best to create in ArcGIS Online first, then reuse that clientID in Portals - there's a minuscule chance that you might come up with a duplicate clientID and ArcGIS Online has by far the larger population of duplicates to conflict with.  Take a look at the instructions at How To: Add Survey123 for ArcGIS as a registered application to Portal for ArcGIS 10.3.1  and pretend you're app & appID are being used in place of Survey123's. The other issue that is common to experience in this situation is not have a valid redirect_uri - remember to have that included (like the well-known string urn:ietf:wg:oauth:2.0:oob for native apps) ... View more