nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Updated to 25.2.1 and cannot edit any features with True Curves

AndrewDeLuca

My staff updated to version 25.2.1 and now any features that have a curve in their vertices, lines or polygons, cannot be edited in field maps in my services published from a registered data store in our 11.1 enterprise environment. Simple features such as those with 4 vertices and no curves can still be edited. My iPad is on 25.1.X and can still edit the features fine with the same map and feature service. Is there a new setting in field maps I am missing to configure the ability to edit features with true curves? I dont even want my staff to edit the geometry, just the attributes.

Is field maps considered a non compatible true curve client in 25.2.X but not 25.1.X?

Find more posts tagged with

Accepted answers

ColinLawrence

Hi @AndrewDeLuca , can you give this a shot in Field Maps 25.2.4 that was just released? Attribute editing should now be enabled for true curve features. We were able to get this in a bit sooner than anticipated!

All comments

AndrewDeLuca

Are you attempting to edit geometry or just attributes of true curve features? They only fixed editing attributes - editing geometry of true curve features in field maps is no more.

JJuliano11

We are still experiencing this issue in Field Maps 25.2.5 for iOS devices. We are in version 11.5 Enterprise.

GIS_System_AdministratorSunshi

thank you so much for this. We had similar issues where we couldnt edit curves. We tried everything above. Updating today to the latest version resolved our issues

ColinLawrence

Hi @AndrewDeLuca I understand the frustrations and I apologize. This is work we have in progress but due to the revolving patches we are working on and a planned release to align with the AGOL release later this month it is hard to say where this will make it in. Its most likely to be in the 25.3 release which could be as early as October 22 (AGOL release) but I cannot say that is concrete at this time.

AndrewDeLuca

Hi Colin, thank you for getting back to me. I just spent the last few weeks standing up a workflow using field maps to verify asset data and capture pictures as attachments for thousands of assets across several feature classes in field maps. In order to do that, my staff need to use field maps as it is the only product in the ESRI stack that can do this workflow in the field effectively that I am aware of.

Based on what you are telling me, I have two options - Densify my data across thousands of records in many feature classes to ensure there are no true curves, or wait an unspecified amount of time for you all to implement functionality I had in a previous version of the application. Are those the only two options you see as well? Can you give me a more concrete timeline for the attribute only updates of true curve features?

ColinLawrence

Hi Andrew

>Is field maps considered a non compatible true curve client in 25.2.X but not 25.1.X?

Field Maps 25.1 was "destroying" true curve features in order to edit them so it was not a compatible client. When the feature is submitted it is override with line/vertex approximations. Field Maps 25.2 is now enforcing a harder restriction here but there are plans to separately allow editing of the attributes of true curve features, as you mention.

AndrewDeLuca

I have tried overwriting the service with "Only allow true curve updates with true curve clients" and neither checked nor unchecked allow editing of records with true curves through field maps.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.