Latest Contributions by ZacharySutherby

Hello @JavierCMartínezPrieto,  Are you looking to automate survey publishing using the XLSForm as the template, or automate the survey design in the XLSForm?  ... View more

Hello @LydiaWerner_MAC,  If you are looking to extract the z location from the geopoint in your Survey123 survey there is a pulldata("@geopoint") property to do that. Please see this table for all possible values that can be extracted from geopoint locations. This will pull the z value from the devices location.  Taking a look at the screen capture if you're looking to extract a known z value from the attribute of a feature you can use a JavaScript function to query the feature service based on the geopoint location. Please refer to the JavaScript sample in Connect for an example of how to extract information from a feature service based on a geopoint location.  ... View more

Hello @AmeWunderle,  If you could pass along a copy of the XLSForm that would help with troubleshooting on our end. Do you see a difference if you already have the Survey123 app open in the background and link to it vs launching Survey123 fresh from Field Maps?  If you see the same behavior with Survey123 open in the background can you please enable diagnostic logging in the Survey123 field app and then link to it from Field Maps? Obtaining a copy of the diagnostic log will also help with understanding what's happening when Survey123 tries to open the survey.  ... View more

Hello @GarrettRSmith,  A couple of options are:  - Save your XLSForm as a new survey, make the changes you need, then append the records from survey A to survey B - Another option (likely more friendly for your use case) would be to modify the feature service directly (add new fields directly to the feature service), if any of the fields need to be renamed you can add it as a new field with the updated name and then field calculate the value. Once the feature service schema is as desired you can make the updates to the surveys XLSForm and republish.  Please refer to this table for more information as to what changes in your XLSForm would require recreating the feature service.  ... View more

Hello @explocarto,  It is possible to send an applyEdits request to a feature service directly from a JavaScript function in Survey123. I would suggest using an application called Postman which is an API development tool to narrow down the syntax needed in the applyEdits request, then translate that to your JavaScript function.  In the JavaScript sample we have in Connect we demonstrate a few ways to work with online API's. We don't explicitly demonstrate sending an applyEdits request, but using the samples available in Connect and the working request from Postman they can be merged. An important consideration is asynchronous calls are not supported in JavaScript functions so setting the async parameter in the open() method to False is needed.  ... View more

Hello @WillWoodroof,  Would you be able to pass along a copy of the JavaScript file for troubleshooting on our end?  ... View more

Hello @10KYIGIS,  The workflow may depend on the OS of the device, for example if the user is on an IOS device if they press and hold on the sqlite file in the Files app there's an option to compress it which will create a zip file. They can then email that zip file or upload it to a cloud sharing platform. If there's not a native way on Android it may be possible to use a third party files app that will allow them to zip the file and pass along.  ... View more

Hello @neomapper,  A Field Maps update shouldn't impact linked content in Survey123. Can you please explain a little more about what exactly is broken with your linked content? What do you have linked to your survey and what is the behavior observed?  ... View more

Hello @BrandonA_CDPH,  On the second line of the fourth code block is where we are exporting the data as an Excel spreadsheet. The code is as follows:  item_excel = rel_fs.export(title=survey_by_id.title, export_format='Excel') The export method in the Python API supports a "parameters" argument which we aren't using in the sample provided. I believe in this "parameters" argument you can set up a where clause to only export records where [Field] = XYZ.  Please see this documentation for more information on how to configure the parameters, but setting the "parameters" argument to something like:  parameters= "{"layers" :[ {"id" : 0, "where" : "fieldname = XYZ*"}]}" Should allow you to export a subset of records. You may need to convert it to a JSON object, please see this link for more information on converting the syntax to a JSON object ... View more

Hello @NASAHarvest,  Are you taking the survey in the Survey123 field app or the Survey123 web app?  ... View more

Hello @AdriannaBarton,  Our 3.14 April release just went out today (3.14.255) is you check on the new version is the same behavior observed?  If so would we be able to obtain a diagnostic log when the form loads to review on our end?  ... View more