Latest Contributions by BamJam

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

Thank you guys for such a quick response and solution. We create the .csv file using Pandas in a python script. A simple fix for this was to set index=False when creating the .csv file, which eliminated the empty header in column A. Would not have known to apply that change without your testing and solution. Thanks again! Brandon

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

Sent via email... Thanks

Survey123 version 3.12.274 Pulldata() functionality changes?

Hello Survey123 Community and @JamesTedrick or @IsmaelChivite We have a form that has been in use for months that utilizes the pull data functionality to populate some fields in the form based on a barcode scan. We have had several users call that are not getting data populated in those fields after a barcode scan. All our users are using iOS devices. We have isolated this issue to users that have version 3.12.274 of Survey123. We've verified that the necessary .csv file is in the media folder within the Portal item and that the data is properly populated in the file itself. Furthermore, users that are still on 3.11.164 are able to scan and get the necessary fields populated...even after updating the form itself. So, it seems to be an issue with version 3.12.274. I have not been able to find any information on version 3.12.274. Is there a change in the pulldata() functionality? Any help would be appreciated. Thanks, Brandon

‎01-22-2021

Once they complete the survey, if they are offline, it will place the survey in the Outbox as you mention. Unfortunately, opening that survey again and and making changes just applies edits to the same survey (record). We need to be able to create a completely new survey from the same existing record in the Inbox. Once the user has selected a survey from the Inbox, and completes that selected survey, whether it is in their Outbox or Sent, it is no longer available in the Inbox until they refresh. This is preventing them from being able to complete an additional survey for that same existing record from the Inbox.

‎01-21-2021

We have several surveys that utilize the inbox functionality. In our design, the inbox is the parent record, and we are capturing related data in a repeat. The repeat (related data) are inspections done at facilities. In some cases, these inspections need to be completed multiple times a day at the same facility. The issue we are running into: 1. User opens survey, selects Inbox and refreshes the inbox at the beginning of the day (while in cell coverage) 2. User selects an inbox record, and completes an inspection (This causes the inbox record that they selected to no longer be available). 3. Later in the day, the user needs to complete another inspection for the same facility, but cannot due to the record no longer being available (and they do not cell service to be able to refresh the inbox). Is there a way to keep all the inbox records even after there has been a survey completed for the records?

‎09-11-2020

Carlos Krefft: Typical user...

‎09-11-2020

Doug, That is a creative workaround. I think in my case I'd prefer to avoid the potential for confusion with the users having to delete repeats. The whole repeat portion of the form seems to be the most difficult for our users to grasp. Adding nested repeats is even more confusing to them. I ended up using a hosted feature service that has the schema Survey123 is expecting with the _count fields where necessary. Then, I use FME to sync the data from the hosted data store to my Oracle database nightly, ignoring the _count field in the hosted service.

‎09-11-2020

Hello Disha, I was not able to resolve the issue with the _count field in Oracle. The workaround I came up with was to use a hosted feature service with Survey123, then sync the data collected in the hosted data store to my enterprise Oracle geodatabase using FME on a nightly basis. This allows the Survey123 app to honor repeat count and have the necessary _count field in the hosted feature service. I ignore the _count field in the hosted feature service when syncing the data to my enterprise Oracle database. Hope that helps, good luck!

‎05-08-2020

I ran into this issue and was able to resolve it by removing the request to be returned in json format. So, change the url in the request: Original line: data_url = " <portalurl> /<webadaptorname> /sharing/rest/content/items/ {0} /data/?f=json&token= {1} " .format(itemID, agol_helper.token) New line: data_url = "<portalurl>/<webadaptorname>/sharing/rest/content/items/ {0} /data/?token= {1} " .format(itemID, agol_helper.token)

‎12-19-2019

I have put in the request. Thanks for the suggestion.

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by BamJam

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

Survey123 version 3.12.274 Pulldata() functionality changes?

Re: Keep all inbox records...even after completing

Keep all inbox records...even after completing

Re: Limit repeat count in Survey123 without the _count field in schema

Re: Limit repeat count in Survey123 without the _count field in schema

Re: Limit repeat count in Survey123 without the _count field in schema

Re: Updating the media folder of a Survey123 Form item

Re: Survey123 Inbox search via barcode