Latest Contributions by Billy

The markup layer is a very convenient tool to draw ideas on maps and to keep track of data all in one place. When using one markup layer, there is no problems using the tool as it was designed. The problem comes when a user is switching between multiple markup layers. A user would want to use a different markup layer to keep track of different markups in the same location without them being connected. Once a user is done with one markup layer and wants to use a different markup layer, the map will zoom all the way out, and to get back to where the user was drawing, they would have to zoom back in. This circumstance occurs every time a user would switch between markup layers. It makes more sense to keep the screen where it is when switching between markup layers rather than zooming the screen out when switching between markup layers. I am not sure if this is a bug or is intended by Esri, but it would be a lot more convenient for the screen to stay where it is when switching between markup layers. This happens on the IPad mobile application.  ... View more

Hi,  I'm not sure if this is the right place to post this question but I'm using the action scripting feature inside the Utility Network Editor (UNE) from ESRI UK (Utility Network Editor - Take Your Utility Network Everywhere | Esri UK). The action scripting in UNE uses Arcade to trigger actions in the app. The syntax provided in the help documentation to "zoom to" a location is this:  // Pan to a Location return { command: "zoomto", geometry: Extent({ xmin: 1000, ymin: 1000, xmax: 1000, ymax: 1000, spatialReference: { wkid: 102100 } }) };  We are trying to use the code below. This code is trigger after using the Find functionality of the app and selecting one item in the search results. When we validate the code we get this for line 4: Execution Error:  Cannot read properties of null (reading 'spatialReference'). It looks like the Extent function is having a problem processing the geometry of the selected feature. When we comment-out line 4 and remove the "zoomto" command, the rest of the code works. The feature is selected, the map pans to the selected feature, the selected feature flashes; but no zoom to.         var feature = $action.matchedFeature; // Get the selected feature var featureGeometry = Geometry(feature); // Get the geometry of the selected feature var extent = Extent(featureGeometry); // Calculate the extent of the selected feature's geometry // If the feature geometry is null, return an empty extent if (IsEmpty(featureGeometry)) { extent = Extent({xmin: 0, ymin: 0, xmax: 0, ymax: 0, spatialReference: {wkid: 102100}}); } // Select Features return [ // Select the search feature { command: "select", method: "new", layers: [ { layerid: $action.matchedlayerid, graphics: [$action.matchedfeature] } ] }, // Pan to a Location { command: "panto", geometry: featureGeometry, flash: true }, // Zoom to a Location { command: "zoomto", geometry: extent } ];       ... View more

Hi,  I'm using Survey123 Connect Version 3.19.104 and the survey is used in the mobile app only.  I want to create an Inbox Query expression using a DateTime question. I tried different date-time formats in the SQL expression with no luck and I haven't found any documentation on how to this. I'm getting "Code 400 Cannot perform query.  Invalid query parameters." What is the query syntax for this type of questions? Regards.    ... View more

Hi,  Error happening on Android and iOS devices. Survey created with Survey123 Connect version 3.18.123.  Windows and Android Survey123 Mobile app version 3.18.145. To clarify, when the survey is submitted without using the Draft or Outbox folders NO error is raised. The error is raised when the survey is sent to the Draft or Outbox folders, and then submitting the survey from there.  The Android or iOS mobile app does not show an error description, but I turned on the logging feature on the Android app and this is the error that appears at the bottom:  After getting this error, I installed the Windows Survey123 Mobile app and tried to replicate the error there, but the survey was sent without a problem from the Draft or Outbox folders. Then I moved the sqlite database from the Android device to the Windows Mobile app and I was able to restore the data and submit the survey from the Outbox folder without getting the error.  Finally, I went back to the Android mobile app and deleted the survey raising the error from the Outbox folder. Then I tried to replicate the error with a new survey, but this time there was no error.  It seems that the issue disappeared, but I think this type of issues solve themselves. These are the questions that I have:  What is the reason for this error that shows intermittently? What could have happened that seemingly solved the issue after copying the sqlite database to the Windows Mobile app and submitting the survey from there? Why the error was raised on Android and iOS, but not in the Windows Mobile app? The Survey123 Troubleshoot documentation (Troubleshoot—ArcGIS Survey123 | Documentation) has this reference to a "400" error code, but if there is a Schema problem with the database, why I can submit the survey when not using the Draft or Outbox folders? I can provide the full log file if needed.  Regards.  ... View more