Latest Contributions by BamJam

‎12-18-2019

We have a form with the inbox enabled. One of the attributes is a barcode id. We would like to allow the users to have the ability to scan the barcode in the inbox search to get to the record. Is this possible?

‎12-10-2019

James, Our issue with adding this field to the feature service is that our back end DBMS is Oracle, and all field names are created with all uppercase characters. Unfortunately, Survey123 Connect creates the _count field in all lowercase, which is preventing the publishing from completing due to the case mismatch. I have tried to run the alter field gp tool to change the case of the field in the feature class, but it does not change. I've also attempted this workaround to accomplish changing the case of the field, but it did not work either. So, it seems I don't have control to change the case of the field name in our Oracle db, or in Survey123 Connect. Even though the field exists in our feature service, Survey123 Connect will not recognize it. Any suggestions on how to get around this?

‎12-06-2019

That explains the _count field being generated by S123 Connect regardless of what I enter in the repeat_count field. In an attempt to publish my survey, I have created the necessary _count field in my feature service. However, the field name is all uppercase in my Oracle db and thus the feature service. This is preventing my survey from publishing due to the _count field that is automatically created by S123 Connect being all lowercase: Is there a way to control the case of the _count field that is created by S123 Connect? Or, ignore case of the fields in the feature service when publishing? Btw, I have tried to change the case of the field in my Oracle db, but it will not allow me to do so. Thanks, Brandon

‎12-05-2019

I survey that is using a submission url with an existing feature service and I am trying to limit a repeat count to 1, but avoid the _count field being included in the schema. I've read that this is possible by referencing another field in the repeat_count column. I have attempted this, but it seems to add the {repeat}_count field to the schema regardless of what I enter in the repeat_count column of the repeat question. Does anyone have an example form that limits the repeat count of a repeat question, but does not require the _count field to be added to the schema?

‎12-04-2019

James Tedrick, Can you please provide an xlsx example of the workaround that allows for limiting the repeat count without having to have the _count field in the feature service referenced in the submission url? I would like to limit my repeat to 1, but am not able to avoid the _count field being required in the feature service. Thanks!

‎02-23-2017

Hello All, I am trying to utilize the output connector, 'Push JSON to External Website' in order to execute a gp service that is published on our ArcGIS Server. The gp service has one parameter called json, which expects a gpstring. I am able to execute the gp service without issue when I provide a string via the gp service's submitJob url: I have the output connecter configured with the intent of pushing the GeoEvent json to my gp service via the post method: This will actually send the request to my gp service, but the json is not posted, which results in the gp service failing. I've tried the Post body MIME Type as application/json, but still get the same result. It does not seem as if there are any options for the actual post body except for MIME type. If I look at a sucessful request to the gp service, I see that the form data has all the possible parameters included (with the most important being json): Is there a way to configure the existing Push JSON to External Website to work with a gp service on ArcGIS Server? Thanks in advance, Brandon

‎02-15-2017

Mitchell, I would have continued to assume we were on 1.7 or 1.8. Thanks for the clarification!

‎02-15-2017

Hello Mitchell, I think I may have missed the obvious way to check the Survey123 app version that a template is based on. I was not able to determine which version of the Survey123 app the template was based on by downloading, opening and viewing the about info. What I saw (and still see today) was the version that was assigned by the developor in AppStudio: Not the actual Survey123 app version that the template was based on. The Survey123 template available today in AppStudio now includes this information, but still allows the developer to assign their own versioning of their versions of the app they deploy from AppStudio: . So, I while I can easily obtain this information from the templates today, I still am not able to determine what verison of Survey123 that our previos deployment was based on other than correlating the date that we downloaded the template with the version history of Survey123. Based on this, since we downloaded the template in AppStudio and deployed in October 2016, I have to assume that the template was based on Survey123 version 1.7.20 (released 8/31/2016) or 1.8.21 (released 9/28/2016). Is there another way to determine what version of the Survey123 app that a template was based on? Obvious or not? Thanks

‎09-01-2016

Is there a way to identify what build version of Survey 123 the templates in AppStudio are based on?

‎10-20-2011

Good to know that 9.2 doesn't support a method to access xy coordinates directly (maybe one day we will upgrade). I was able to get the data populated, but will try these other methods in the future. Thanks for all your help!

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by BamJam

Survey123 Inbox search via barcode

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

Re: Delete/Hide repeat_count fields on feature service

Limit repeat count in Survey123 without the _count field in schema

Re: Delete/Hide repeat_count fields on feature service

Push GeoEvent JSON to Published ArcGIS Server GP Service

Re: Survey123 Template build version in AppStudio

Re: Survey123 Template build version in AppStudio

Survey123 Template build version in AppStudio

Re: Field calculator problem