Latest Contributions by JamesTedrick

Hi Tony, Enhanced reporting capabilities are something that we want to support, but don't have any specific timelines yet to be able to share. ... View more

Hi Tucker, Using the pulldata function was how I originally tested the calculation capability and discovered the bug I noted above. ... View more

Hi Chris, We currently have known issues with connecting to Active Directory secured portals- this looks like one of the symptoms of that. ... View more

Hi Brian, Surveys authored in Survey123 Connect aren't supported by the current web form client.  There is a new web form client in beta that can be used; to access it, preview the survey in Survey123 Connect, click on the globe button and select 'Open in web app'. James ... View more

Hi Cassandra, Can you verify that the survey was published?  The log file you provided indicates the problem occurred in downloading the survey; we've seen this happen when a survey was authored on the website but not published.  You may also want to go to the item's detail page in the 'My Content' section of ArcGIS Online and attempt to open it there. ... View more

Hi Craig, A slight change was made in terms of how the table name is specified at 1.10.  The 'form_id' entry in the settings worksheet must match the name of the layer that the form writes to.   ... View more

Hi Elizabeth, The steps to fix are to allow data to be submitted successfully from that point forward; it doesn't affect the already submitted data. ... View more

On sum() - you're correct, we don't have id documented; it's generally used in context of the repeat (as you mention in point 2) and would add all the values for a given question across repeats.  It also appears to work if you pass a sequence of questions (for example, sum(${Provyta1},${Provyta2},${Provyta3},${Provyta4},${Provyta5},${Provyta6},${Provyta7},${Provyta8},${Provyta9},${Provyta10},${Provyta11},${Provyta12},${Provyta13},${Provyta14},${Provyta15},${Provyta16},${Provyta17},${Provyta18})  ) but gives warning on XLSForm validation. I'll try to reproduce the bind::type issue you describe on iOS/Android. I would think number(${Field1}) would be faster because ${Field1}*1implies conversion to number and then multiplication, but haven't tested it. ... View more

Hi Elizabeth, It looks like you loaded the original table item.  Check your 'My Content' page and click on the survey's folder - you should see 3 or 4 items: - a Form item - a Feature Layer (hosted) item - this is what you've loaded - 1-2 Feature Layer (hosted, view) items - the one with 'stakeholder' is the one to modify. ... View more

Hi Erik, Is it possible to create a select_one from your LicenseNumber column and test that? I'm not seeing anything obvious (unless there's extra white space in some values- you might want to open the CSV in a text editor and check). ... View more

Hi Steve, Currently, it isn't possible.  You may want to post on the https://community.esri.com/groups/workforce-for-arcgis?sr=search&searchId=d12a2319-182c-4a71-97ab-2a9960c4246c&searchIndex=0‌ forum - they are considering enhancements like this. ... View more

Hi Cecilia, The message you are seeing can have several causes.  One of the most common ones is having expired login credentials - can you log out and log in on the app? ... View more

Hi Tucker, I just did a quick test of what you described.  It looks like there's an issue in the calculation of points in repeats- all the points are updated when the parent point is updated. I also logged request to an enhancement of having a hidden point automatically collect the user's location in a repeat, which sounds like what you're trying to accomplish. ... View more

A couple of questions/issues: 1) In a few places, you are specifying the bind::Esri:fieldType value.  These need to match the keyword in the 'types' sheet exactly 2) Much of the complexity of your survey could be reduced by using repeats. (Provtya 1 - 18 groups look like the same questions).   3) I assume the reason you're not using repeats is the summary calculations you do at the end of the form, since Survey123 cannot yet sum over repeats.  It looks like many of your calculations could be simplified by using the 'sum' function, or perhaps those calculations could be generated later than on the form. 4) There seem to be a lot unnecessary bind::type values - they don't need to be set for every question, just the ones where the default type don't match what you want (select_one, calculate).  Removing the bind:type field seems to improve performance a bit. That being said, I do see better performance of the form on iOS then on Android and Mac ... View more