Please prioritise the decoupling of the ability to kill operations in the Real Time Performance Panel from the Data Explorer.

Currently we disable the Data Explorer on our production projects so that our developers can view the Profiler and the Metrics, without being able to query the actual data. But disabling the Data Explorer prevents us from killing operations in the Real Time Performance Panel. While reenabling the Data Explorer is an easy task, it's very easy to forget the one needs to do this in order to be able to kill operations as they do not seem related in any way from a user perspective.
The error message is also not very informative that the problem is the Data Explorer. In fact it mentions only that the user does not have permissions to kill the operation.

A Simple Undo Function.

A Bit Of Background Information

Just talked to Julia from PR. Apparently "undo" is not an available feature.

YES,

there is a backup option for higher tier customers.

But,

I am not asking for a full on log of everything. Just a simple copy of the last added or deleted document in a collection for example. In case you accidentally clicked the confirm delete button on the document, your mouse was happening to hover over, when a spider jumped down from the ceiling and landed on your mouse.
It happens.

Besides the point.

That functionality is not particularly hard to implement, nor will it cut your revenue.

Hear me out.

For atlas (web only) for example:
All that needs to be done is to save a copy of the current document you have handled, be it adding it or deleting it.
Yes,you need not necessarily save a copy of a document you created.

Besides the point.

The copy for said document, will be saved in either in cache, cookie, session storage, what ever your heart's desire.

Be it encrypted or not.

Up to you.

All I am asking is, please, for the love of god, think of the less fortunate once in a while and implement an undo feature.

"But were busy at the moment"

You may as well hire me for the job, this should not take all that long to implement.

Always open for further question or a good discussion.

Sincerely,

A doofus on the job

Especially during testing, when you create masses of bogus, invalid records, would it be nice to have a better interface for batch deletion. Having selected multiple records I should be able to delete them in one go, which is not the case currently. There are multiple way to solve it UI-wise - won't dig into details.

Also, sometimes the whole collection becomes worthless, in which case a button "Clear collection" would be a handy tool.

I understand the safety concerns for collections which are in production. Maybe we could flag project/collection as development/production - in which case some features would be guarded less/more respectively.

Under Atlas > Clusters > Collections I can select a Collection and use the 'Find' option to quickly seek and edit a Document. At the moment the UI display is like JSON, but has stripped out the brackets, which makes copying the data awkward.

Feature 1: The find display UI should offer a JSON mode, so the the Document, or parts of it can be copied in JSON format.

If I select the Edit option, the editing UI is 'intelligent', in that it forces JSON compliance via the various options. However, this makes pasting in new data impossible.

Feature 2: The Find Edit mode, should offer a JSON option, so a whole Document can be added in one paste operation. It could 'translate' this back into the current UI if necessary, much in the same way web HTML editors offer a display or source mode.

UX on Collections view has some problems which are listed below;
- It takes around 10-20 seconds to load the Collections page, specifically the left panel which lists namespaces.
- Then without any user interaction or feedback, it takes another 10 seconds to focus on the top most available namespace to display details of it on right hand side panel
- Then filtering namespaces with "auth" doesn't make any change in the screen and not giving any feedback neither.
- Then inputting more letters "authen" triggers the filtering however this time it filters namespaces which had nothing to do with "authen" keyword.
- Filtering namespaces with "rewards" keyword again returns unrelated namespaces.
- Clicking on one of the filtered namespaces, gives you no feedback about any loading operation and then all of a sudden fills the right hand side with details of the namespace after 7 seconds.
- And sadly after the right hand side panel gets filled with namespace details, you lose your original filtering on left hand side panel.

We would be happy if you can please evaluate and improve UX on Collection view.