Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About PiyaliKundu2
PiyaliKundu2
Esri Contributor
since
07-19-2016
07-06-2026
21
Posts created
7
Kudos given
3
Solutions
37
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(4 Idea Submissions)Latest Contributions by PiyaliKundu2
|
POST
|
Based on your screenshot, nothing would happen. Your screenshot shows that you already have the field esritask_duedate in the schema which is the field we are looking for in order to enable tasks. After enabling tasks, you can use your other Due_date field if you'd like instead. Just make sure to reference that field in the Form and task configuration as you build your layouts and actions. The esritask_duedate field is only required to enable tasks in Field Maps Designer. You don't need to keep it in order for tasks to be used in Field Maps mobile - so you can use your other Due_date field instead after tasks has been enabled.
... View more
02-17-2026
09:53 AM
|
0
|
0
|
1577
|
|
POST
|
Hello @Faiez - I'm a bit confused - which scenario are you referring to when asking whether changing a field name would be okay? With regards to the Field Maps tasks, the field names for the required esritask_ fields must be spelled specifically as stated in the documentation. This is purely because, with this currently release of the capability, Field Maps Designer looks for those fields in the data to build the tasks configuration off of - whether it is by adding them in the enabling process, or the owner of the data manually adding them and the domains prior to enabling. Once tasks is enabled on the layer in Designer, the fields that are required for tasks to function appropriately on mobile are esritask_status, esritask_type, and esritask_assignee. The data owner could technically get rid of the fields for priority, due date, description, and notes and use their own fields for those concepts in the workflow. In the future, we are considering adding the capability to allow users to "point" the tasks enablement process to their own existing fields, so they wouldn't have to add any additional fields if they didn't want to. Hope that helps explain things a bit better.
... View more
02-08-2026
08:01 AM
|
0
|
2
|
1708
|
|
POST
|
Hello @AndreasHall - It appears your Due Date field is incorrectly entered. The field name should be esritask_duedate (duedate being one word). You entered esritask_due_date (with the underscore). Please try deleting the field and re-adding it, and let us know if that works.
... View more
02-06-2026
06:49 AM
|
1
|
5
|
1729
|
|
POST
|
Hi @ModernElectric - Completely understand the frustration with continually needing to replace solutions and re-train workers. While Workforce is planned to be deprecated, as per our announcement , we have no plans to end support for Field Maps. In fact, the plan to integrate Workforce's capabilities into Field Maps has been in the roadmap for both products for over 6 years. It's taken several major updates on the Field Maps side - also hinging on the evolution of the Maps SDK - to reach this point in development. The ultimate goal has been to bring all the capabilities of Collector, Explorer, Tracker, and Workforce into a single app, rather than siloing relatively related capabilities in singular "bite-sized" apps and complicating workflows. Moving forward, Field Maps will continue to be supported and updated regularly as Esri technology continues to evolve. It is our hope that, with the way tasks in Field Maps has been designed, it will be relatively easy for users to transition their workflows over, take advantage of greater flexibility and more advanced capabilities, and make it an easier experience for their users to transition as well through intuitive design. Additionally, utilities users will be able to take advantage of all of Field Maps's support for Utility Network capabilities as well, all within a single app. Should you need it, we are happy to schedule a call to discuss your concerns, workflows, and transition plans and help provide guidance through this process.
... View more
10-16-2025
10:32 AM
|
0
|
0
|
1321
|
|
POST
|
@ModernElectric Understood. Sync is a complicated process that involves many factors - connectivity and data integrity being among them. Field Maps has a few advantages over Workforce in this regard, since it is not only built on the latest SDKs, but has been more updated on the web and mobile side. In terms of configuring your map/data and ensuring it meets offline standards, Field Maps Designer's Offline tab includes a series of checks to ensure that your data/map meet the standards and requirements needed to take the maps offline. And we are constantly updating this series of checks to ensure we are catching all the potential problems (especially as Esri's APIs and SDKs evolve). In terms of connectivity, Field Maps mobile app allows the user to also use both the online map and offline areas (preplanned and adhoc) in tandem rather than being limited to purely one or the other. Similarly, the map author can also prohibit users from these options as well to steer the configuration and user experience in the way that works best with your workflow. Finally, Field Maps supports more methods of configuring your offline data workflows, including being able to configure and leverage multiple preplanned offline areas, using MMPKs for advanced disconnected workflows, sideloading or hosting a custom basemap v/tpks meant for offline use in your portal and reference them in the map so that they are downloaded automatically when the user takes the data offline - to name a few. If issues arise with offline workflows, as always, we encourage users to log and escalate Support tickets so that problems can be assessed from multiple angles by multiple teams and we can identify the source of the issue, whether it is an issue with Field Maps, the environment performance, the data, or something else. In general, I think the most powerful capability of Field Maps over Workforce is the simultaneous online map/offline areas options - therefore, if your worker has connectivity and runs into an offline sync issue, then they can switch to the online map and resume their work there. In terms of resources, in addition to updated Field Maps documentation, you can check out: What's new in ArcGIS Field Maps (25.2.0 release) ArcGIS Field Maps: Introducing Tasks Data Collection Techniques We are also working on short tutorials on tasks as part of our Tips from the Team series. We are also working on crafting documentation and Python scripts specifically on migrating from Workforce to Field Maps. Hope this helps!
... View more
10-16-2025
07:49 AM
|
0
|
1
|
1329
|
|
BLOG
|
Thanks for the update @PaulCone2 ! As always, let us know if you run into any other troubles.
... View more
10-16-2025
06:52 AM
|
0
|
0
|
1916
|
|
BLOG
|
@PaulCone2 - Are your users working from the online map, offline areas (adhoc or preplanned), MMPK and/or in scenarios where they are in low connectivity or possibly completely disconnected?
... View more
10-15-2025
10:03 AM
|
0
|
0
|
1981
|
|
POST
|
Hi @BigLouC - You can continue to leverage and integrate with Survey123 when using tasks with Field Maps. Tasks essentially allows you to add an integration link action to your task layout template (i.e., as a button) so it would operate in the same manner Workforce's integration with Survey123 did (i.e., a button to launch a survey). Furthermore, the nature of that survey can also be more dynamic, as the integration links in tasks can be configured with Arcade, and therefore, dynamically generated based on your other data/factors. In terms of differences in UI/workflows between Survey123 and Field Maps, there are still quite a few differences between the two. Field Maps supports Arcade, but not custom Javascript. So if your survey is pulling data from non-ArcGIS/third party sources, that could be a limitation. Field Maps's Arcade could pull data from other layers in the map or even feature services in the org (via FeatureSet functions), but not third party data sources. Field Maps does not support grid UI, and is vertical scrolling only. It does support grouping of questions in the editable form which can be expanded/contracted and that setting can be set as default. Field Maps currently does not yet have multiple-select question types; however, this is a feature we are working to implement in the future. Field Maps currently does not support graphical signature UI question types, which could be a legal requirement for some forms. The Field Maps UI cannot be custom colored. In terms of the "nested question", I would need to understand that a bit better. Can you provide a screenshot or configuration XLSForm? You can use Arcade calculations to copy answers between form inputs in the editable form. And you could use the new tasks capability's action buttons to copy data from even a related record to a parent feature, but there could be some limitations here depending on more nuances of the nature of your form. All-in-all, I imagine that Field Maps could easily replace Workforce in your situation, as being the means to view assigned tasks in a list, update the status of the task, and open a Survey123 survey. However, it's not clear yet to me if Field Maps could also replace Survey123 for your use case, and I would advise to initially keep the role of Survey123 as-is in your workflow until further testing and exploration could be done to identify any gaps or changes in functionality. In terms of location updates - yes, workers can either opt to share their location or be required to share their location in Field Maps when opening a map - similar to Workforce. The one current difference in sharing location between Workforce and Field Maps is that workers cannot yet share their work status (i.e., Working, On break, Offline) using location sharing in Field Maps. This is something else that is currently under development as we understand this could be an important feature in users workflows. I hope this helps!
... View more
10-14-2025
11:31 AM
|
0
|
0
|
4266
|
|
POST
|
Hello @ModernElectric - Just a quick update that tasks has now been fully released as part of the latest Field Maps update, so it is currently out of beta, in case that helps with testing and implementation. Yes, you're correct - Tasks is a feature in ArcGIS Field Maps mobile app, therefore you would have to change your workflows over to Field Maps. I will note that Workforce is planned for deprecation in Q1 2026 and is planned for retirement in Q3 2026 (link to deprecation notice). Your mobile crews can do most everything that Workforce mobile app can do using the new Field Maps tasks capability including: Updating statuses using a simple button UI; Receive notifications for newly assigned tasks; Link to Survey123 surveys, or other third party systems (using an enhanced and more flexible integration mechanism); Navigate to tasks using ArcGIS Navigator or other navigation apps; Leverage location sharing to track worker locations and even notify them (using Field Maps geofences) when they are close to a new task feature. Best of all, tasks can be enabled on your existing data, can adjust to your schema and data structures with little tailoring and requirements, and can take advantage of all the new advancements in ArcGIS and Field Maps including using view layers, Arcade in calculations and popups/visualization, configurable popup elements and more.
... View more
10-14-2025
11:15 AM
|
0
|
3
|
1338
|
|
POST
|
@apgis16 - Yes, you should have the Inbox enabled. See Prepare to edit existing survey data for more info. Can you confirm the following: Device and operating system Version of Field Maps Version of Survey123 In Field Maps, are you working in the online map or an offline area?
... View more
10-09-2025
02:08 PM
|
0
|
2
|
1834
|
|
POST
|
Hi @apgis16 - Just to confirm your workflow: you have a map in Field Maps with a task-enabled layer, and you would like to open the same feature in a corresponding survey in the Survey123 mobile app. Is that correct? If so, then your first example is a link to the web survey, not the mobile app. And I believe your other two example baseURL links are missing two parameters: q: -> prior to the globalID query update=true -> to leverage the Inbox to open an existing feature. If you adjust your script, it should look like: var baseURL = "https://survey123.arcgis.app?itemID=fe89e89f9ad0409b881b5406acb603ad&action=edit&update=true&q:globalId="
var gID = StandardizeGuid($feature.GlobalID, 'digits-hyphen')
return baseURL + gID The following options should also work: Hard-code the Survey123 link directly into the Link input and reference the GlobalID field using the curly bracket notation (no Arcade expression required): https://survey123.arcgis.app?itemID=fe89e89f9ad0409b881b5406acb603ad&action=edit&update=true&q:globalId={GlobalID} Use an Arcade expression that uses the https://survey123.arcgis.app universal app link. return "https://survey123.arcgis.app?itemID=fe89e89f9ad0409b881b5406acb603ad&action=edit&update=true&q:globalId=" + $feature.GlobalID Use an Arcade expression that uses the arcgis-survey123:// app link. return "arcgis-survey123://?itemID=fe89e89f9ad0409b881b5406acb603ad&action=edit&update=true&q:globalId=" + $feature.GlobalID Please see the following resources for more info on how to craft Survey123 URLs: Launch the field app Use a URL to Open Existing Record to Edit in App (Not Web)
... View more
10-09-2025
12:16 PM
|
1
|
4
|
1855
|
|
POST
|
Hello @BigLouC @ModernElectric - We understand that this experience with Workforce is frustrating and I will forward this BUG case to our product leads to consider. We are also in the process of releasing an enhanced version of Workforce called Tasks within Field Maps with our next mobile release this fall, both of which are built on the latest SDKs. Tasks will provide a far more improved experience and performance as it will be able to take advantage of both, the latest tech in the platform (e.g, view layers, Arcade, popup elements) and support a vastly simplified architecture which will allow users to configure and tailor tasks closer to their desired workflows (e.g., Status values, action buttons, symbology/labels/popups). You can learn more about tasks in our latest blog article, and also join our Early Adopter Program to help beta test tasks before it releases. We definitely encourage all Workforce users to give tasks a try and start checking out the capabilities early, and many Workforce users are already in the beta. We look forward to hearing your feedback about this new capability.
... View more
07-29-2025
09:07 AM
|
0
|
0
|
3275
|
|
IDEA
|
Hello @Jesse - Thank you for sharing this idea. This is a known limitation of ArcGIS Workforce that is addressed with the new field tasks capability being developed in ArcGIS Field Maps. With Field Maps' field tasks capability, you will have more options on how your Decline button (which we call "actions") is configured. You would be able to hook up your Decline action to a single-select prompt with options you have configured. While Field Maps does not yet have select multiple-type form elements, that capability will be coming in the near future. We are excited to announce that field tasks is currently available in a public beta release via the Field Maps Early Adopter program! Please see the following blog for more details on the new task coordination capability and other exciting features coming soon to Field Maps: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here .
... View more
05-23-2025
06:07 AM
|
0
|
0
|
620
|
|
IDEA
|
Hello @ModernElectric - Thank you for submitting this idea. While we do not plan to support a separate Windows desktop application for Field Maps or Workforce at this time, I do think the new field tasks capability we are developing in Field Maps will provide more editing options. A map author will be able to enable a new or existing layer (or view layer) in a map with tasks, making the architecture greatly simplified as it only requires a single geometry-based feature layer in a map. Users with access to that layer and appropriate editing privileges (e.g., Organization Administrators, editors in a shared update group) would be able to edit the attributes of that task feature. Map authors can also leverage view layer filters to further refine which features should be visible to other users in this dispatching/response role. Since tasks run off of regular feature layers, they can be edited in a variety of ways and do not require a specialized dispatching app as Workforce did. As @AndyGeo mentioned above, some of the Solutions have tailored applications for managing and replying to requests (i.e., editing features). You can also configure specialized editing apps via Instant Apps, Experience Builder, Dashboard + Survey123 combinations, and other standard ArcGIS editing interfaces to create or edit the tasks. (For example, we highly recommend the Manager template as a easy and familiar UI for new or non-technical users.) If you truly needed a native desktop application, you could potentially use the following: Survey123 Windows app (using the Inbox capability to search and retrieve features), ArcGIS Pro combined with Pro's Tasks capability to have a streamlined editing experience, ArcGIS for Excel plugin can be used to visualize and edit records in a feature service in a spreadsheet. We are excited to announce that field tasks is currently available in a public beta release via the Field Maps Early Adopter program! Please see the following blog for more details on the new task coordination capability and other exciting features coming soon to Field Maps: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here .
... View more
05-22-2025
02:16 PM
|
0
|
0
|
945
|
|
IDEA
|
Hello @ModernElectric - Thank you for submitting this idea. It seems you would like a few enhancements to your workflows in Workforce, including: To be able to configure specific Status values and labels that better match your workflow and industry terminology, For other users with correct privileges (e.g., Administrators) to be able to interact with and change an assignment's status in the back office. Am I understanding these enhancement requests correctly? If so, I believe that the new field tasks capability we are developing in Field Maps will meet these requirements. Firstly, a map author will be able to enable a new or existing layer in a map with tasks, making the architecture greatly simplified as it only requires a single geometry-based feature layer in a map. As such, users who are given access to that layer and have the appropriate editing privileges (e.g., Organization Administrators, editors in a shared update group) would be able to edit the status of the task feature. Map authors can configure editing apps using Instant Apps, Experience Builder, and other standard ArcGIS editing interfaces to create or edit the tasks. The tasks capability can also be enabled on view layers, so map authors can leverage view layer filters as well to further refine which features should be visible to other users. Second, tasks will enable map authors to configure Status values and labels that better align with your workflows and industry standards. Map authors can configure the Status field to be string or numeric, can add however many status values they need, and can configure the value labels to fit your needs. We are excited to announce that field tasks is currently available in a public beta release via the Field Maps Early Adopter program! Please see the following blog for more details on the new task coordination capability and other exciting features coming soon to Field Maps: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here .
... View more
05-22-2025
01:53 PM
|
0
|
0
|
855
|
My kudoed posts
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-09-2025 12:16 PM | |
| 1 | 02-06-2026 06:49 AM | |
| 1 | 02-01-2023 09:06 AM | |
| 2 | 07-14-2017 08:24 AM | |
| 2 | 07-14-2017 08:24 AM |
Activity Feed
- Got a Kudo for Re: Issue launching Survey123 from Field Maps Task Layout — “Survey link is invalid or requires an app that isn’t installed”. 02-18-2026 01:40 PM
- Posted Re: Enable referenced Feature Layer for task on ArcGIS Field Maps Questions. 02-17-2026 09:53 AM
- Got a Kudo for Re: Enable referenced Feature Layer for task. 02-09-2026 02:09 PM
- Posted Re: Enable referenced Feature Layer for task on ArcGIS Field Maps Questions. 02-08-2026 08:01 AM
- Posted Re: Enable referenced Feature Layer for task on ArcGIS Field Maps Questions. 02-06-2026 06:49 AM
- Kudoed Re: Workforce Project Sync Delay & Ongoing Issues for ModernElectric. 10-16-2025 11:11 AM
- Posted Re: Workforce Project Sync Delay & Ongoing Issues on ArcGIS Workforce Questions. 10-16-2025 10:32 AM
- Posted Re: Workforce Project Sync Delay & Ongoing Issues on ArcGIS Workforce Questions. 10-16-2025 07:49 AM
- Posted Re: ArcGIS Field Maps 25.2.0 released! on ArcGIS Field Maps Blog. 10-16-2025 06:52 AM
- Kudoed Re: ArcGIS Field Maps 25.2.0 released! for PaulCone2. 10-16-2025 06:51 AM
- Posted Re: ArcGIS Field Maps 25.2.0 released! on ArcGIS Field Maps Blog. 10-15-2025 10:03 AM
- Posted Re: Workforce Project Sync Delay & Ongoing Issues on ArcGIS Workforce Questions. 10-14-2025 11:31 AM
- Posted Re: Workforce Project Sync Delay & Ongoing Issues on ArcGIS Workforce Questions. 10-14-2025 11:15 AM
- Posted Re: Issue launching Survey123 from Field Maps Task Layout — “Survey link is invalid or requires an app that isn’t installed” on ArcGIS Field Maps Questions. 10-09-2025 02:08 PM
- Posted Re: Issue launching Survey123 from Field Maps Task Layout — “Survey link is invalid or requires an app that isn’t installed” on ArcGIS Field Maps Questions. 10-09-2025 12:16 PM
- Posted Re: Workforce Project Sync Delay & Ongoing Issues on ArcGIS Workforce Questions. 07-29-2025 09:07 AM
- Posted Re: Field validation for declined reason on ArcGIS Workforce Ideas. 05-23-2025 06:07 AM
- Posted Re: PC Windows application for desktop users on ArcGIS Workforce Ideas. 05-22-2025 02:16 PM
- Posted Re: Editing control on Assignment STATUS on ArcGIS Workforce Ideas. 05-22-2025 01:53 PM
- Posted Re: Workforce Project Sync Delay & Ongoing Issues on ArcGIS Workforce Questions. 12-03-2024 01:58 PM
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-06-2026
01:33 PM
|