|
POST
|
@HayleeCrowle – It looks like you may have used the Wildlife Reporter template in the QuickCapture designer as the starting point for your project, then updated the button labels in the Appearance tab, but not the attribute information in the Data tab. As a result, the attribute information you were expecting wasn’t captured. Unfortunately, if the information wasn’t submitted at the time, it isn’t possible to retrieve it afterwards. Going forward, updating the attributes in the Data tab should ensure the correct information is captured.
... View more
2 weeks ago
|
0
|
1
|
69
|
|
POST
|
@Pili - You are right that QuickCapture only allows a single user input per page. This is by design to allow simple and rapid data capture. For multiple input types (or questions) on a single page, we would recomend the use of ArcGIS Survey123.
... View more
2 weeks ago
|
1
|
1
|
138
|
|
POST
|
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.
... View more
05-05-2026
04:58 AM
|
0
|
0
|
221
|
|
POST
|
@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.
... View more
04-15-2026
09:29 PM
|
1
|
0
|
394
|
|
POST
|
@ALBJORGUI Please submit this as a bug to Esri support.
... View more
04-15-2026
08:34 PM
|
1
|
0
|
365
|
|
POST
|
@SueBoelk Please work with your enterprise admin on this. It sounds like an SSL a certificate error for the problematic device.
... View more
04-15-2026
08:23 PM
|
0
|
0
|
185
|
|
POST
|
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.
... View more
04-15-2026
08:17 PM
|
0
|
1
|
256
|
|
POST
|
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!
... View more
01-19-2026
08:21 PM
|
0
|
0
|
475
|
|
POST
|
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.
... View more
01-19-2026
07:51 PM
|
1
|
1
|
617
|
|
POST
|
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
... View more
12-21-2025
05:51 PM
|
0
|
0
|
527
|
|
POST
|
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
... View more
12-21-2025
05:48 PM
|
0
|
0
|
373
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 04-15-2026 08:34 PM | |
| 1 | 04-15-2026 09:29 PM | |
| 1 | 01-19-2026 07:51 PM | |
| 2 | 12-21-2025 05:34 PM |
| Online Status |
Online
|
| Date Last Visited |
5 hours ago
|