Select to view content in your preferred language

ApplyEdits error (!2d!)

765
2
Jump to solution
07-16-2024 09:37 AM
Alison_Mynsberge
Occasional Contributor

Hi,

We are unable to apply edits to a feature service, and while the response is simply

{
    "error": {
        "code": 400,
        "extendedCode": -2147024809,
        "message": "Unable to complete operation.",
        "details": [
            "Unable to perform applyEdits operation."
        ]
    }
},

The server logs show

"Edit for Feature with ObjectID: 112 for Layer: !2d! is not applied."

This feature is not m- or z-enabled that I can discern.  Any suggestions?

0 Kudos
1 Solution

Accepted Solutions
Alison_Mynsberge
Occasional Contributor

The issue was related to the DateTime formats:

The Date/Time formats retrieved by a query to an ArcGIS REST endpoint differ from the format required for submitting an update or new record to an ArcGIS REST endpoint.  We referred to discussions in https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/proper-rest-query-for-epoch/td-p/... and https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/turning-an-esrifieldtypedate-fiel....

We modified the data for the date fields so that they were submitted as epoch instead of as a formatted date/time. 

 

Why the date/time format issue came back with that particular server log is completely unclear.

View solution in original post

0 Kudos
2 Replies
Alison_Mynsberge
Occasional Contributor

The issue was related to the DateTime formats:

The Date/Time formats retrieved by a query to an ArcGIS REST endpoint differ from the format required for submitting an update or new record to an ArcGIS REST endpoint.  We referred to discussions in https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/proper-rest-query-for-epoch/td-p/... and https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/turning-an-esrifieldtypedate-fiel....

We modified the data for the date fields so that they were submitted as epoch instead of as a formatted date/time. 

 

Why the date/time format issue came back with that particular server log is completely unclear.

0 Kudos
Nick_McCausland
Emerging Contributor

Hey Alison, 

 

We just got this error message for a published feature service today in Field Maps. Your post was the most recent I could find on the topic. When you say "We modified the data for the date fields so that they were submitted as epoch instead of as a formatted date/time." what do you mean by epoch? Sorry for the ignorance, but I haven't seen anything about epoch before. Not sure why its all of a sudden not able to read a date field. I figured the data was just corrupted and was causing the issue. 

 

Thanks for your help. 

-Nick

0 Kudos