[IMPLEMENTED] Can't upsert a previously deleted document

Feature Requests Implemented Features
1

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

If I try to upsert a document that I previously deleted through the UI, I get the following error:

{
  "message": "Object has already been deleted.",
  "traceId": "00-620df20bca942847965aa4ea148a1a3e-091c89e9c52dd347-00",
  "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
  "statusCode": 400
}

Expected behavior

I would expect the object to be recreated. Is this a mongo feature we can get around that I’m not aware?

Environment

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version
2

This is not a bug. It is a restriction of the custom ID system and the fact that nothing really gets deleted.

There are several solutions for this issue, that could be implemented:

  1. Implement hard delete: Schema Contents Deleting & Bulk Insert

  2. Allow the upsert system to undelete the content item.

  3. Introduce a new feature to “undelete” a content item.

  4. Allow the create operation again when a content is deleted, so it start the flow from beginning basically.

I would prefer 1 and 4. From the logical side they are identical.

2 Likes
3

It is implemented but not part of the cloud yet

4

This topic was automatically closed after 2 days. New replies are no longer allowed.