Hello, last week I was able to upload the markup layer to AGOL, which allowed me to use it in Pro and export it to a geodatabase. Today, I collected more markup, now called "personal markup", and could not find a way to upload to my AGOL account. The version of Field Maps on my phone appears to have automatically updated within the past few days. I have Version 25.2.0 on an iPhone 12 with iOS 18.6.2.
If it's no longer possible to upload the markup layer to AGOL, how can I bring the markup into ArcGIS Pro?
Thank you,
Ryan
Hi Ryan,
The ability to share markup directly to the organization in Field Maps has been officially retired. You can review the deprecation and retirement notice here: https://support.esri.com/en-us/knowledge-base/deprecation-arcgis-field-maps-sharing-markup-to-organi...
In Personal Markup in the new generation of Field Maps, users can share it peer-to-peer but can no longer share it directly to the organization. It would be great to hear more about your specific scenario, if you are able please share your use cases for sharing markup to the org so we can learn about your needs. It might also spur some other ideas for us to suggest here to help you satisfy this workflow ...
Thanks for your question and your feedback
Heather
Hi Heather,
This has come as a bit of a shock for our organisation as well. We have over 80 Field Maps users across the business doing mapping of ecological and archaeological features. The ecologists in particular like to use markup to capture data on site that doesn't fit within our enterprise schemas and are unexpected, so can't easily be planned for ahead of time. They like the ease and flexibility of using mark up to capture this, especially as the polygon editing experience in Field Maps is less than idea for capturing natural features with complex boundaries.
They were sharing these markups with the GIS team by being able to upload them our portal. They were also able to view their markup alongside other maps that had additional layers that we don't want to push to every field map due to their drag on the efficiency and reliability of Field Maps.
We now appear to have no way to access the markup data in Pro or in web maps and will have to rapidly figure out work arounds and new methods to achieve the same goal.
Kind regards,
James.