(bug) Can't edit "estimated year" (Request failed with status code 400)

DmitriyBryndin

Editing "estimated year" results in "Unable to save data" error message.

From the 400 error returned, it looks like there is a bug in UI.

100% reproducible every time I need to correct the estimated year. E.g. for this person

https://www.familysearch.org/ark:/61903/3:1:3Q9M-CSSM-19GK-S?view=index&action=view&cc=4135959&personArk=%2Fark%3A%2F61903%2F1%3A1%3A6VTD-V993

Since there is no input field for "estimated year" I have to click "+ Add more information" for "Date", delete the current "Estimated Year(1816)" , add new "estimated year". Then the input field appears, where I can enter "1766". Trying to save I get the "Unable to save" error message.

Here's the 400 error

{
"message": "Request failed with status code 400",
"name": "AxiosError",
"stack": "AxiosError: Request failed with status code 400\n at je (https://edge.fscdn.org/assets/static/js/7131.ffe7efc7291469d6.js:2:3072036)\n at XMLHttpRequest.v (https://edge.fscdn.org/assets/static/js/7131.ffe7efc7291469d6.js:2:3076994)\n at pt.request (https://edge.fscdn.org/assets/static/js/7131.ffe7efc7291469d6.js:2:3085239)\n at async It (https://edge.fscdn.org/assets/static/js/main.c1e89536d2db25f0.js:1:449985)\n at async Pt (https://edge.fscdn.org/assets/static/js/main.c1e89536d2db25f0.js:1:448960)\n at async Object.onClick (https://edge.fscdn.org/assets/static/js/main.c1e89536d2db25f0.js:1:654074)",
"config": {
"transitional": {
"silentJSONParsing": true,
"forcedJSONParsing": true,
"clarifyTimeoutError": false
},
"adapter": [
"xhr",
"http",
"fetch"
],
"transformRequest": [
null
],
"transformResponse": [
null
],
"timeout": 0,
"xsrfCookieName": "XSRF-TOKEN",
"xsrfHeaderName": "X-XSRF-TOKEN",
"maxContentLength": -1,
"maxBodyLength": -1,
"env": {},
"headers": {
"Accept": "application/json",
"Content-Type": "application/json",
"FS-User-Agent-Chain": "RIP-shared-image-viewer",
"Accept-Language": "en",
"Authorization": "Bearer p0-zLyR6RmAIqy.IT2pMQTwMnI"
},
"method": "post",
"url": "https://sg30p0.familysearch.org/service/records/volunteer/orchestration/sls/actions",
"data": "{"actions":[{"partitionKey":"3:1:3Q9M-CSSM-19GK-S","id":"4e4420a1-7209-4910-9b73-3d524eb1a2c5","elementType":"FIELD","opCode":"CREATE_ELEMENT","elementArg":{"elementType":"FIELD","partitionKey":"3:1:3Q9M-CSSM-19GK-S","id":"4e4420a1-7209-4910-9b73-3d524eb1a2c5","fieldType":"YEAR_EST","value":{"id":"033f2606-954f-47d7-a515-9ac859cd8d76","origValue":{"text":"1766","attribution":{"comment":"","reasonId":127170,"app":"RII"}}}},"journalAttribution":{"app":"RII"}},{"partitionKey":"3:1:3Q9M-CSSM-19GK-S","id":"4e4420a1-7209-4910-9b73-3d524eb1a2c5","elementType":"FIELD","opCode":"ADD_FV","fieldValueArg":{"id":"033f2606-954f-47d7-a515-9ac859cd8d76","origValue":{"text":"1766","attribution":{"comment":"","reasonId":127170,"app":"RII"}}},"journalAttribution":{"app":"RII"}},{"partitionKey":"3:1:3Q9M-CSSM-19GK-S","id":"f80809ae-c0fc-452c-9396-8b4718c1a0e8","opCode":"ADD_SUB","elementType":"DATE","referenceArg":{"partitionKey":"3:1:3Q9M-CSSM-19GK-S","id":"4e4420a1-7209-4910-9b73-3d524eb1a2c5"},"journalAttribution":{"app":"RII"}}]}",
"signal": {}
},
"code": "ERR_BAD_REQUEST",
"status": 400
}

TheoDarwin

I see the same, with the addition that my 400 response comes with a Java stack trace and error message that indicates that the Estimated Year field is not editable on the back end:

java.lang.IllegalArgumentException: Invalid action modification for action ingest. Field Type YEAR_EST is not editable
at org.familysearch.sls.logic.ActionLogic.checkForModifyingInvalidFieldType(ActionLogic.java:104)
at org.familysearch.sls.logic.ActionLogic.checkForInvalidUserActions(ActionLogic.java:90)
at org.familysearch.sls.controllers.ActionsController.ingestActions(ActionsController.java:91)
...

DmitriyBryndin

This clearly is a bug, but I don't see a way to report bugs. Only this forum and some contact email. Do you know a way? I'd love to have it fixed.

DmitriyBryndin

Apparently, I can use the "feedback" button, which was broken for me for a long time.

It works when ad-blockers are disabled. Just saw a similar question on the forum. Go figure