Latest Contributions by JakeMatthys

‎12-15-2016

Thanks Craig... That was our issue. - Jake

‎12-14-2016

I have noticed an issue with the Dispatch webpage today. It is unable to display workers when clicking on the workers tab at the bottom of the control. We have workers loaded into our project and they were able to complete receive and complete work today using the worker app, but from the dispatch web page, we could not see any workers and the work could not be displayed by worker. Did a change happen to the webpage? Could this be a data issue on our end, even through the Worker App seems to be working fine? Thanks, - Jake

‎12-06-2016

I would like to follow up on this issue as it relates to repeaters with required fields and the repeaters are exposed to the user based on the relevant answers to previous questions. Unfortunately we did not find that using default values in all of the repeaters that meet the above criteria as a valid solution for our use case because we would have overhead in terms of managing the default values and checking for the default value presence to exclude them from downstream reporting. The two main issues that we have encountered with repeaters that have required fields and the repeaters are exposed to the user based on relevant answers to previous questions. (version 1.9.24): A survey that has a repeater with required fields, but that has not been exposed to the user because the repeater has a relevant that was not satisfied, will prevent a survey from being submitted In a situation where a survey has multiple repeaters, each with required fields and each repeater is relevant on a previous question. In the case where more that 1 repeater is relevant (based on users previous answers) as long as 1 of the repeaters has all of the required fields satisfied, than the required fields in the other repeaters are ignored. Meaning that the required fields in the other repeater do not behave, you can leave some of the questions null and the survey will still submit.

‎11-21-2016

Thank you for the recommendations Ismael. We will test the default values and let you know if that solution will work for us. Also, thanks for the recommendation on the inspection_type constraint using the 'count-selected' function. - Jake

‎11-21-2016

Thanks for the quick reply Ismael. That seems like a viable alternative and is a path we may pursue to allow for form flexibility while being able to retain existing data. Thanks for explaining the best practice. - Jake

‎11-17-2016

Plus 1 for this issue...

‎11-17-2016

Hello, We recently released a Workforce Project into a production environment for utility inspections and the two most frequent requests that we are getting from the users are the following. Add a filter that allows that allows users of the worker app to be able to only view those assignments that are due today. This filter already exists in the dispatcher app, but the workers would like this ability as well. Maybe this is something that could be applied in the To Do/Completed filter choice list Add the ability to sort by due date in either ascending or descending order. Currently the default is ascending, but having an option for descending would be helpful for our users. Thanks, - Jake

‎11-17-2016

As our organization begins to increasingly utilize Survey 123 for data collection, I would like ask about the vision that ESRI has for Survey 123 schema changes. Currently a schema change means that existing data, associated with the survey undergoing a schema change, will be lost. In the future do you envision the ability to add questions to a survey and re-publishing that survey without losing the existing data stored in the cloud? Currently we replicate our Survey data down to our enterprise database, but we have had discussions about using the Survey 123 feature layer as our permanent storage, but we do not want that to prevent us from making survey schema changes (adding a question here or there as business needs arise). - Jake

‎11-17-2016

Just wanted to give a bump to this issue. We have approximately 25 surveys in use and our only gripe is that required fields inside of repeaters are not being enforced. Thanks for hearing out our concern and hopefully a fix is coming in the near future. - Jake

‎09-22-2016

Thanks for the info Mitchell. Please keep us posted when you believe the issues with required fields in repeaters is resolved.

‎09-19-2016

I have a survey which has some required fields, the survey also has a number of repeaters and these repeaters also have required fields. The form has a multi select and each repeating option is relevant to the multi select. So if the user selects 3 items, lets say pipes, valves and hydrants, the user will get 3 repeating sections to populate. We are experiencing an issue where the required fields are enforced in the first repeater, but is not enforced in subsequent repeaters. In the first repeater, if all required fields are populated, the form can be submitted, if not, the form identifies the required field that needs populated. This holds true for all repeat occurrences within that first repeater. In the subsequent repeaters the required fields are not validated by the UI. What we are finding is that as long as the user has populated all the required fields in the main form and in the first repeating section, required fields that have not been populated in subsequent repeater sections are submitted by the form. I would expect the form to not submit and to warn the user that required fields have not been populated. Has anyone else experienced this issue? I have uploaded the excel form document if anyone would like to take a look. Thanks, - Jake

‎08-25-2016

Sorry for the delayed response. This publish was to AGOL. I new question was added to the survey. My guess is that the cause is my management of the Survey, really just looking to see if any others have experienced this issue. Management of Surveys through a Dev, Test and Production environment is something that we are struggling with.

‎08-18-2016

I made a schema and form change to an existing survey (added a new column) and published this change. I was expecting the typical warning that the schema will change and data will be lost, but instead I got the 'Survey will be published without affecting existing data'. I published the survey and then investigated the results. I noticed that the form had a new timestamp, but the feature layer did not. When testing the form contains the new question and input, and submits successfully to the feature layer, but the new data does not have a column in the feature layer, so that data does not get captured. How did I get the form and feature layer out of sync? I have experienced this issue with other surveys in the past few days, is this an issue with my management of the surveys or a known bug? Thanks for any input. - Jake

‎07-27-2016

I am using Survey123 Connect version 1.6.11 and I am unable to get default values to work in a repeater. Is this still a known bug? Do we have an ETA on a resolution? Thanks - Jake

‎07-09-2016

Is it possible to create hidden question types with default values? I have tried this in a survey, but when the survey is submitted and I review the data from the rest endpoint, the hidden question contains a null value rather than the default value. Am I doing something incorrect?

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by JakeMatthys

Re: Dispatch Webpage not displaying Workers

Dispatch Webpage not displaying Workers

Re: Issue with Required Fields Inside a Repeater

Re: Issue with Required Fields Inside a Repeater

Re: Survey 123 vision for schema changes

Re: "Continue this survey" results in duplicate records?

Filter by Due Today and Sort by Due Data descending in Workforce

Survey 123 vision for schema changes

Re: Issue with Required Fields Inside a Repeater

Re: Issue with Required Fields Inside a Repeater

Issue with Required Fields Inside a Repeater

Re: Publish Updated Form but not Schema

Publish Updated Form but not Schema

Re: Default values and calculations not working in Repeat

Hidden question type with default values

Re: ArcGIS Pro 3.5.6 patch -- Now Available

Re: Survey123 Webhook not always firing

Re: Survey123 Webhook Sometimes Doesn't Fire

Re: Expression Symbology in Dispatcher

Re: Workforce Sync Error - Unable to syncronize re...