Latest Contributions by BrandonArmstrong

Hi Nick, yes, this is possible. Please take a look at the following documentation Webhooks—Survey123 for ArcGIS | ArcGIS  Brandon ... View more

Hi Caroline, I was able to reproduce the behavior that you mentioned.  It appears that it is related to applying rules to questions that reside within a Group.  I have gone ahead and raised an issue in our internal repository, but in the meantime, a workaround might be to remove the questions from the group and delete the 'Group' question. Best, Brandon ... View more

Hi Jonathan, I have attached an example of a pulldata calculation working against a choice from a select_one question.  Please take a look and see if this is helps you.  If this does not help you, please provide the zipped folder as an attachment to this thread, or I can provide you with my email upon request. Best, Brandon ... View more

Hi James, We currently have an existing enhancement in our backlog related to the behavior you describe.  I will add your comments to it. Best, Brandon ... View more

Hi Roger, I have been unable to reproduce the issue using Survey123 Connect v. 3.0.142 and the Survey123 Field App v. 3.0.149 (current release versions). Can you please verify that these are the versions of the app that you are testing with, and if so, provide your XLSForm to us for testing?  If you cannot upload it to the thread, let me know and I will send you a private message with my email address. Best, Brandon ... View more

Please take a look at the response from Zhifang Wang‌, in the following GeoNet thread which speaks to some of the variations related to the error that you are encountering... Just FYI, whatever the input is (single or batch records), "Save result to your account" or not, as long as you see the "print map failed for {question name} {"error":{"code":500..." error message, this means the concurrent limitation of the behind printing service is met. Trying again later may fix the issue. However, there are also some facts currently you may want to know: Currently, no matter if there's geopoint question in your survey (published from the web designer or Survey123 Connect), a request will be sent to the backend printing service per record. Hence, the more records you include in one request, the more easier you will see above error message If the generated report exceeds 10MB and you didn't choose to "Save result to your account", you will see the "{"message": "Internal server error"}" error message. This is an independent limitation to the above one, which means you can only see this error after the report has been successfully generated. We are working on both of issues for 3.1 release (planned in mid of October), please staty tuned to our blog ... View more

Hi Carl, After saving the web map you shared with me, I was able to successfully use Explorer and Survey123 with the pop up containing the custom url scheme in the following environment...  Samsung Galaxy S8 Android v.8.0 Explorer v. 18.1.0 Survey123 v.3.0.149 Can you please verify that you were using the same?  Also, is there is specific record that exhibits this behavior, or is it when launching your 'Inspection Form' from any of the records containing a pop-up? Best, Brandon ... View more

Hi Brandon, I am still not able to see these fields after creating the survey from the attached XLSForm using Survey123 Connect 3.0.142 and Survey123 Field App 3.0.149.  Please try to reproduce this behavior by publishing the same XLSForm from scratch and submitting with the Field App.  Let me know what you see after trying this. ... View more

Hi Brandon, nice name indeed! After creating a survey based off of the attached XLSForm and submitting a few surveys using the field app, I do not see any of the fields that you've set to null in the resulting feature service.  Are you stating that the fields that you listed (PrePack, Refrigerated, ShelfStable, PkgSizeOz, PkgNum, SampleSize6) have been created? If so, where are you viewing the data? (Survey123 website or ArcGIS Online)? ... View more

Hi Brandon, You are correct in your assumption that setting the bind::esri:fieldType to null should prevent the field from being created in the database, while allowing for it to be seen in the form.  Can you please share your XLSForm and provide details as to the field which is unexpectedly showing? Thanks, Brandon ... View more

The next update to Survey123 should occur by the end of next week.  Please do feel free to try out the Beta version to ensure that the behavior is resolved, if you have the time! Best, Brandon ... View more

Hi Matt, Can you please take a look at the following Forum Thread and see if this is consistent with the behavior that you are encountering? If it is related to data not appearing in the first repeat, but showing in sequential repeats, the fix will be applied very shortly and can even be accessed now via our Early Adopter Community: Welcome to our Feedback Community  Best, Brandon ... View more