Latest Contributions by JohnathanHasthorpe

Hi — @GISMapLad The behaviour you’re seeing may be due to a known configuration issue that can affect offline workflows with attachments. Why this can happen In QuickCapture, features and attachments are submitted as separate requests. In situations where connectivity is intermittent, it’s possible for a feature to be successfully sent, but the associated attachment upload fails. This behaviour is dictated by whether the feature service supports applyEdits using GlobalIDs. You can check this by inspecting the service’s REST JSON for the following property: supportsApplyEditsWithGlobalIds If this property is set to false, attachments are uploaded after the feature has been created and are not guaranteed to be successfully added. In low‑bandwidth or unreliable network conditions, this can result in the feature being created even though one or more attachments subsequently fail to upload. However, when supportsApplyEditsWithGlobalIds is set to true, the behaviour is much more robust: The feature is only sent once all attachments have been successfully uploaded If any attachment fails, the feature is not sent, allowing the app to retry the entire submission later In other words, enabling this property ensures that features will not be missing attachments. To find out how to do so, see the following blog: How to enable supportsApplyEditsWithGlobalIDs on your feature layer For hosted feature layers in ArcGIS Online, enabling Sync is often enough to resolve this. For non‑hosted or Enterprise layers, the same requirements apply as outlined in the Survey123 guidance referenced in the blog. Controlling when records are sent This can be achieved using the app’s Autosend setting. If Autosend is enabled, QuickCapture will attempt to upload records at a defined interval whenever the app is online. To avoid this: Disable Autosend in the app settings Records will remain on the device until the user explicitly sends them (from the map page), for example once they are back on a stable Wi‑Fi connection You should also note that Auto Send can be set using an organisational setting, meaning it is possible to enforce the setting for all users in your organisation. Can the images be recovered? Unfortunately, once a feature has been marked as successfully sent and the local record has been deleted, the attachments can’t be recovered. However, you should be aware of the following organization setting: Retain sent records. This prevents data from being deleted from the device after sending, and allows you to use data recovery to recover missing records. Summary Based on your description, this issue is very likely related to a combination of: Intermittent connectivity during upload Automatic sending when a weak connection becomes available A feature service where supportsApplyEditsWithGlobalIDs is set to false Ensuring that this property is enabled is the most important step for preventing attachment loss in offline QuickCapture workflows.

‎04-15-2026

@GISNCC - Arcade expressions like this require the project map to be opened in order to run. To conserve battery and system resources, QuickCapture does not automatically load the map in the background. As a result, the map must be opened by the user at least once. After the user leaves the map and returns to the project page, autosend should resume as expected.

‎04-15-2026

@ALBJORGUI Please submit this as a bug to Esri support.

‎04-15-2026

@Wags2012 - Could you share your device details?

‎04-15-2026

@SueBoelk Please work with your enterprise admin on this. It sounds like an SSL a certificate error for the problematic device.

‎04-15-2026

Hi @Gene_Sipes - Upload intervals less than 30 seconds are not supported in QuickCapture. In the QuickCapture Designer the options are 1 minute, 15 minutes or 1 hour.

‎01-19-2026

Hi James — a couple of things to check: 1) Esri default (green) map behavior To validate this flow end‑to‑end: Uninstall the app, then do a fresh install. Download a project that uses a web map as its map. Open the project offline. You should see a message that the map failed to load. Tap USE DEFAULT — you should then see the Esri default (green) map. 2) MMPK with online layers If your MMPK references online web layers, you must be online when opening the map to load those layers. Could you confirm: Does your MMPK include any offline tiles (TPK/TPKX/VTPK) or offline feature layers? What specific layers are packaged in the MMPK (basemap, feature layers, rasters, elevation, etc.)? This will help us determine whether the behavior you’re seeing is expected or if we need to adjust packaging or connectivity assumptions. Thanks!

‎01-19-2026

Hi Katie, Yes, this will work. You just need to create a project user input in Settings: Once it’s created, you can select one or more buttons in your project, go to the Data tab, and apply the project user input to the appropriate field. The same project user input can be used across multiple buttons, even if they send data to different layers. The only requirement is that the field you’re updating is a text field. Let me know if you run into any issues.

‎12-21-2025

Hi @usace_sam_rd3 This behaviour is not expected, and I was unable to reproduce it on my side. Could you please log a support case so we can investigate this issue further? Thanks, John

‎12-21-2025

Hi Kevin, Thank you for reaching out. This functionality isn’t available in the current version of the QuickCapture mobile app. However, we’re in the process of rebuilding the app from the ground up, and the new version will include this feature to meet our accessibility requirements. Thanks, John

‎12-21-2025

Oriented Imagery in QuickCapture Oriented imagery has transformed how field photos are used in GIS workflows. With ArcGIS QuickCapture, we made it incredibly easy to capture the metadata needed to support oriented imagery—such as location, heading, pitch, and roll—without adding complexity for field users. This means every photo collected in the field can be more than just an image; it becomes a spatially aware resource that can be explored in context, projected onto a map, and analysed from multiple angles. By enabling Oriented Imagery Layer in QuickCapture projects, authors can unlock powerful capabilities like situational awareness, asset inspection, and immersive visualisation. The best part? It takes only seconds to enable, and QuickCapture automatically handles the heavy lifting—capturing all required properties behind the scenes. This integration allows field users to keep their workflows simple while making their photos far more useful and actionable across the ArcGIS platform. The retirement of Oriented Imagery Classic The retirement of the Oriented Imagery Catalog (OIC) item is approaching fast and with it comes the deprecation of the oriented imagery clients that you have been working with. Of note is the fact that with the February 2026 ArcGIS Online release, the Oriented Imagery Classic widget will be removed from Experience Builder, and support for OIC in the JavaScript SDK will end. If your workflows depend on these clients, you must now migrate to the newer integrated capability. The integrated capability uses the new Oriented Imagery Layer, which offers much better ArcGIS platform integration and long-term support and enhancements. The good news for QuickCapture users is that the option to enable layers for this capability has been available since 2024, and the transition process from an existing OIC catalogue to the new layer type is simple — here’s what you need to know. Retirement timeline January 2025: Oriented Imagery Classic officially deprecated. No new features added since February 2024. February 2026: ArcGIS Online release removes the Oriented Imagery Classic widget from Experience Builder. Any apps using the Classic widget will break. 2026 (full retirement): Oriented Imagery Classic catalogue data model will no longer be supported. Users should migrate OICs to Oriented Imagery Layers using ArcGIS Pro tools or Esri migration workflows. What about QuickCapture? From November 2025, the Oriented Imagery (Classic) option was removed from QuickCapture Designer. You are no longer able to enable layers for Oriented Imagery (Classic). If you previously enabled the Classic option for a project layer, you will no longer see the “View Oriented Imagery (Classic)” option in QuickCapture Designer. (If you want to explore an existing Oriented Imagery Classic item in the Oriented Imagery Classic Explorer app, you will need to go directly to the app. The application remains available for now.) Any point feature layer that was enabled for Oriented Imagery (Classic) can also be enabled for Oriented Imagery Layer. This means upgrading a QuickCapture project already using the Classic version is very simple—just one click. Migration steps The migration process involves creating new fields in the point feature layer (to accommodate schema changes), mapping the appropriate QuickCapture variables to them, and copying values from old fields to new ones if features already exist. Finally, a new Oriented Imagery Layer item will be created, ready for use in modern oriented imagery client applications. Open your project in QuickCapture Designer. Navigate to Project Settings → Layers. Enable Oriented Imagery Layer for your point feature layer. QuickCapture will automatically: Add the new required fields. Migrate existing data. Create the Oriented Imagery Layer. Save your project and ask your field users to download the update. What about my existing Oriented Imagery apps? Experience Builder apps using the Classic widget: Will break after February 2026. You must rebuild apps using the Oriented Imagery Viewer widget and Oriented Imagery Layers. ArcGIS Pro add-in: For now, you can still view existing OIC items using the add-in in ArcGIS Pro 3.6 or below. However, we recommend upgrading your QuickCapture projects to use the new layer type so you can utilise the built-in oriented imagery tools available in ArcGIS Pro 3.2 and above to future-proof your workflows. Esri-hosted Oriented Imagery Classic Explorer app: For now, you can still view existing OIC items. However, we recommend upgrading your QuickCapture projects and using the built-in oriented imagery tools available in the ArcGIS Map Viewer or ArcGIS Instant Apps (Sidebar and 3D Viewer templates). Resources ArcGIS Equivalency Update for Oriented Imagery Classic Retiring the Oriented Imagery Classic widget (coming soon) QuickCapture documentation Call to action Start your migration today to avoid disruptions in February 2026. If you have questions or need guidance, join the discussion in Esri Community or contact the Esri support team. Future-proof your workflows and make the most of your field photos with Oriented Imagery Layer!

‎12-01-2025

This option makes the mobile app use an external browser on the device for sign in instead of the default in app sign-in page. Using an external browser for sign-in can improve security, support complex enterprise authentication, enable single sign-on, and ensure compliance with modern identity standards. See the following: https://doc.arcgis.com/en/quickcapture/help/organizationsettings.htm#ESRI_SECTION1_2EBD2780FF204DE8B4459B4680F50426

‎12-01-2025

Adding storm drains and manhole covers to the QuickCapture map Yes, this is possible. To do this: Create a web map that includes: The non-editable reference layers (storm drains, manhole covers). The layers used in your QuickCapture project (if you want to see captured data). Save the web map. In your QuickCapture project settings, go to Map Settings and set this web map as the project map. Viewing photos after submission in QuickCapture Unfortunately, QuickCapture does not support web map pop-ups. This means you cannot view photos for features that have already been submitted within the app.

‎12-01-2025

@MR-QE QuickCapture only supports photo uploads through the feature attachment workflow. The ImagePath field is intended to inform oriented imagery clients where the imagery is stored — it does not tell QuickCapture where to store them.

‎12-01-2025

@peterverwey_ses - It is not possible to change the text size for the hint. We will look at this as an enhancement for the next gen version of the mobile app.

Online Status	Online
Date Last Visited	yesterday

My Ideas

Latest Contributions by JohnathanHasthorpe

Re: QuickCapture loading everything BUT the Attachment when Offline

Re: Quick Capture - records not being sent automatically when online but includes arcade expression

Re: Time filter messes with map on the app

Re: Start time Device Variable Not Working Properly

Re: User receives Error when trying to access project

Re: QC Updates LKL More Frequent Than 30 Seconds?

Re: Offline Map Configuration

Re: Using the same project user input for different layers

Re: Missing Attributes Under Capture Fields

Re: Change default font size in for data collection questions

Migrating from Oriented Imagery Classic to Oriented Imagery in ArcGIS QuickCapture

The retirement of Oriented Imagery Classic

Retirement timeline

What about QuickCapture?

Migration steps

What about my existing Oriented Imagery apps?

Resources

Call to action

Re: What is the underlying purpose of the "Use external browser for sign-in" option?

Re: Add & use background Non Editable layers

Re: Is it possible to change Image Path from FA to a URL in Quick Capture?

Re: Is it possible to change the text font size for a Button User Input Hint

Re: Time filter messes with map on the app

Re: Quick Capture - records not being sent automat...

Re: Using the same project user input for differen...

Migrating from Oriented Imagery Classic to Oriente...

Re: Is it possible to change the text font size fo...