Do not lose aggregation pipeline when switching to another collection or database
AdminMassimiliano
(Admin, MongoDB)
shared this idea
I'm excited to share that we released a change in version 1.43.3 that prevents a modified aggregation tab from being closed by accident. Please let us know if you continue to have issues related to losing work when navigating within Compass.
-
Mohamed
commented
I agree 100% The current behavior is so terrible. lost my work multiple times and continue to loose it everytime I code my aggregation in Compass directly. The safest workarround I have found till now is to code "blindly" my aggregation in a separate IDE then copy/paste it in Compass. Fixing this UX mis-behavior will save multiple hours for me.
-
Mark
commented
This is a terrible UX that also applies to just plain queries. A filter with many properties -- gone in a split second with no warning when you click in the wrong place.
-
Richard
commented
This issue has been around for too long. It's a terrible experience for new users, learning how to write aggregations. Regular searches have a 'recent' list, all is needed for now, is adding the same functionality to the aggregation tab.
-
Venkata Suresh Kumar
commented
Had lost all the query content when I tried to open a new collection. It is so frustrating to lose couple of hours worth coding just like that. Please resolve this as soon as possible.