Version control revert issue

[jitendra5792]

Getting the following issue on reverting uncommitted changes. We are using MongoDB storage.
Any suggestions to troubleshoot this?

MongoServerError: Updating the path '@odata' would create a conflict at '@odata' at UpdateManyOperation.execute (/app/node_modules/mongodb/lib/operations/update.js:101:19) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async tryOperation (/app/node_modules/mongodb/lib/operations/execute_operation.js:203:20) at async executeOperation (/app/node_modules/mongodb/lib/operations/execute_operation.js:73:16) at async Collection.updateMany (/app/node_modules/mongodb/lib/collection.js:231:16) at async Object.update (/app/node_modules/@jsreport/jsreport-mongodb-store/lib/provider.js:236:19) at async persistChanges (/app/node_modules/@jsreport/jsreport-version-control/lib/main/versionControl.js:172:29)...

[admin]

It seems like your stored data got a bit corrupted, maybe with some custom ODATA calls?

There should be no @odata stored in the db, that is likely causing the issue.
Can you please try to find which odata call adds that attribute to the entities?
Thank you

[JannetGen]

Reverting versions can definitely be a bit nerve-wracking when the UI doesn't seem to sync up right away. If you're still having trouble seeing the changes or just want to double-check the file structure before committing to another revert, I've found that using a quick online text or metadata extractor can help you verify exactly what's in the report definition. It’s a nice way to troubleshoot without cluttering your local environment.