|
BLOG
|
QuickCapture projects in Survey123 Mobile Earlier this year, we announced that the current generation ArcGIS QuickCapture mobile app is being deprecated and will be retired at a future date. Importantly, this is not a deprecation of QuickCapture as a product. QuickCapture projects continue to be authored in the QuickCapture designer, and the big-button data capture experience remains an important part of ArcGIS field operations. The next step for QuickCapture mobile workflows is Survey123 Mobile, the next generation field data collection app built on modern technology. Survey123 Mobile is designed to open both Survey123 surveys and QuickCapture projects, bringing smart forms and rapid data capture together in one app. Why Survey123 Mobile? Many organizations already use Survey123 and QuickCapture side-by-side. Survey123 is used when the workflow needs a smart form, validation, calculations, repeats, conditional logic, or a more guided data entry experience. QuickCapture is used when the workflow needs fast, simple, big-button capture with minimal interaction. Survey123 Mobile brings these two experiences closer together. Instead of asking mobile workers to install, sign in to, and move between separate apps, the goal is to support both types of work from a single mobile app. One app to install and manage. One sign-in experience for mobile workers. One place to access smart forms and rapid capture projects. Tighter integration between Survey123 surveys and QuickCapture projects. A modern foundation for incremental improvements over time. Combining rapid capture and smart forms One of the most useful patterns is to start with a QuickCapture project and then open a Survey123 survey when more detail is required. A mobile worker can capture common observations quickly using big buttons, then launch a survey for the cases that need structured follow-up information. This can be configured using link buttons in QuickCapture. A link button can open a Survey123 survey using the Survey123 app link or custom URL scheme. You can also use URL parameters to configure the experience so that, after the survey is submitted, the user returns to the QuickCapture project. Example workflows: Roadside observations and detailed inspections. A crew uses big buttons to rapidly capture common roadside issues such as potholes, damaged signs, or debris. If a button represents an issue that requires a full inspection, it opens a Survey123 form where the worker can add photos, assess severity, record measurements, and submit a more detailed report. Environmental monitoring and incident reporting. A field team records routine observations with QuickCapture buttons while moving through a site. When they encounter an exception, such as erosion, contamination, or an access issue, a linked Survey123 survey guides them through the additional information needed for investigation and follow-up. Event operations and public works. Staff use rapid capture to record common operational observations during an event or maintenance run. For specific cases, such as a safety concern or asset damage, they open a Survey123 form to capture a structured assessment, assign a priority, and provide supporting details. Damage assessment and triage. Teams can quickly classify observed damage using big buttons, then open a Survey123 survey when a more complete assessment is required. This allows rapid situational awareness and detailed reporting to work together without changing apps. What works today, and what comes next The first releases of Survey123 Mobile are not intended to provide full parity with the current QuickCapture mobile app. We still have work to do. Some QuickCapture capabilities are available today, some are in development, and others are planned for future releases. That is why customer testing and feedback are so important at this stage. We are adding functionality incrementally, and your feedback will help us understand which QuickCapture capabilities matter most for your workflows as you plan your migration. To check the current status of QuickCapture capabilities in Survey123 Mobile, review the QuickCapture capability documentation. This documentation identifies which functionality is available, in development, planned, or not planned. How to test your projects in Survey123 Mobile The latest Survey123 Mobile beta builds are available through the Survey123 Early Adopter Community and will typically include features and fixes before they are released through the app stores. If you’re new to EAC, you will need to create an account first (Sign up for the Survey123 Early Adopter Community). You can also download Survey123 Mobile from the app stores and the Survey123 resources page to test your existing workflows using the most recent public release. When testing, start with the QuickCapture projects that are most important to your organization. Open each project in Survey123 Mobile, try the most common capture paths, and note any gaps that would prevent your team from migrating. Share your feedback through the EAC feedback channel: Which project types work well today? Which buttons, inputs, variables, or capture patterns are not yet supported? Which capabilities are required before you can move your users to Survey123 Mobile? Which improvements would make the combined Survey123 and QuickCapture experience better for your teams? Note: You do not need to reauthor your existing projects to test them in the beta app. Your projects will appear on the app’s downloads page. We need your feedback We know migration planning depends on confidence. Customers need to understand what is supported today, what is coming next, and what changes may be needed for existing projects. Your testing will help us prioritize the QuickCapture capabilities that matter most. Please use the Early Adopter Community to share feedback, report issues, and tell us which QuickCapture capabilities you need to successfully move your workflows to Survey123 Mobile. This is a transition, and we want to make it a successful one. Survey123 Mobile gives us a modern foundation for the next generation of field data collection, while preserving the value of rapid, big-button capture. With your feedback, we can continue to improve the experience and help organizations bring their QuickCapture and Survey123 workflows together in one place.
... View more
yesterday
|
2
|
0
|
56
|
|
BLOG
|
@clill The QuickCapture designer does not create an Oriented Imagery layer item. Instead, it creates a layer view from the original QuickCapture project layer. This layer view contains the properties required for use with the new Oriented Imagery clients. I've updated the blog post to make this clear. The reason for this is that the current version of the QuickCapture mobile app does not support the new Oriented Imagery layer type. We are currently rebuilding QuickCapture on .NET and plan to add support for this layer type in a future release (it remains part of the Esri roadmap). It's also worth noting that QuickCapture functionality will be incorporated into Survey123 Mobile. Can you confirm whether you're experiencing issues with the layer view itself? If so, could you provide more details about the problem and let us know which Oriented Imagery client you're using? Thanks John
... View more
3 weeks ago
|
0
|
0
|
50
|
|
IDEA
|
06-25-2026
06:56 PM
|
0
|
0
|
88
|
|
IDEA
|
This has been implemented in the QuickCapture Designer.
... View more
06-25-2026
06:51 PM
|
0
|
0
|
81
|
|
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
06-24-2026
08:59 PM
|
0
|
1
|
144
|
|
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
06-24-2026
08:51 PM
|
1
|
1
|
231
|
|
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
|
264
|
|
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
|
452
|
|
POST
|
@ALBJORGUI Please submit this as a bug to Esri support.
... View more
04-15-2026
08:34 PM
|
1
|
0
|
412
|
|
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
|
213
|
|
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
|
283
|
|
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
|
516
|
|
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
|
687
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | yesterday | |
| 1 | 06-24-2026 08:51 PM | |
| 1 | 04-15-2026 08:34 PM | |
| 1 | 04-15-2026 09:29 PM | |
| 1 | 01-19-2026 07:51 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|