Latest Contributions by JohnathanHasthorpe

Hi Mathew, The issue relates to the fact that the portal is configured to allow both https and http access. We will release a fix for this in 1.8 (due for release early December), but for now, if you disable http access for on your portal you should be able to sign in. See: Configure HTTPS—Portal for ArcGIS | Documentation for ArcGIS Enterprise  Please get back to us if you have any further questions. Thanks John ... View more

Hi Ela The data is not lost. It is possible that this behavior is a result of sending over poor network connectivity. Please try the following: - Close and re-open the QuickCapture app (in iOS double-tap the home button and then swipe the app up to close, then tap the app icon to re-open). - Open the project - the sending icon should no longer be stuck. - Go into the map and if there are any records still on the device, press the send button. - If there are many records this could take a while, but they should all send now you are on WIFI. If there were any errors generated, then you could use the data recovery workflow, but in your case, it does not sound necessary. Please let me know how you go. Thanks John ... View more

Update on this: 1.7 (due for release next week) has a fix for the runtime issue mentioned above. You should be able to use this build on your Tab 4 device. ... View more

Hi Bryan - make sure that you also update the sharing for the feature layer items as well as the project - go to the feature layer item in your enterprise portal to do this.  ... View more

Hi Anthony, While this workflow is not supported directly in the app there are a couple of options to achieve this: 1) Post-processing in desktop. Use a spatial join to update the records captured in QuickCapture with the information from the road segments. 2) Use webhooks. At a high level, you could create a scenario that would update the attributes of the captured record with information from the roadway segment that it intersects. However, as it is unlikely that your captured points exactly intersect the line, you may need to create a buffered version of your roadway layer. In doing this you could then use the same approach as that outlined in Example 2: https://community.esri.com/community/arcgis-quickcapture/blog/2020/06/04/data-enrichment-with-arcgis-quickcapture-and-integromat. Please let us know if you need any further information. Thanks John ... View more

Hi Steve It does not matter if you use the beta version of the mobile app and your team uses the current version - as long as the project has been created using the production version of the QuickCapture designer. If you created a project using the QA version of the designer, you could in theory add functionality that is only supported in the beta version of the mobile app. In this case, your users would need to use the beta version of the app in order to access it. However, the project should still open if they stay on the released version. I hope this helps John ... View more

Hi Megan QuickCapture will not know whether it was launched from Collector, nor is there a way to prevent a user from capturing data/opening a project. However, if you are populating the project user input through a custom URL, the user would need to enter the parcel ID themselves if they went direct to QuickCapture. If you made the user input optional and free text, is it likely that the user would enter a value? If so you could filter out all submissions that don't have a parcel ID. You could also add a hint informing the user that the input should only be populated if the project was launched from QuickCapture. Please let me know if the above works for you. If not we will be keen to see if any enhancements good be made to support such workflows. One option for this could be to have an option to make the project user input hidden (if optional) so that it could only be populated via a custom URL. Thanks John ... View more

Updates: - The issue where the user can't open an offline basemap, if the app was opened with the device is offline has been fixed in 1.7 (due for release in mid-September 2020). - The issue with the back button does not affect all Android devices and will be addressed in 1.8. ... View more