Converting Set to Collection Creates Unwanted Unremovable Links to Random Objects

What’s The Bug?

I turned a Set into a Collection.
In the result I’ve got a Collection with lots and lots unwanted connections in the Graph to Objects that shouldn’t be connected to it.
And there is seemingly no way to undo that. :frowning:

How To Reproduce It

  1. Have a (first) Collection that contains a Set as well as some Objects.
  2. Filter the Set for some of the Objects inside the (first) Collection.
  3. Now convert the Set into a second Collection!

Image or Video

Uff, while recording a video that shows the effect in a test Space … because of another bug it affected my main Space!!! :frowning: :frowning: :frowning:
Now I have a big problem … therefore no video!

The Expected Behavior

I expected to have a Collection that shows the same Objects a the original Set did before the transformation of that Set into a Collection.

I don’t expect to have MANY links from the new Collection all MANY other Objects!

Maybe it’s the presence of the View “All” that caused the problem?

  • I can’t say no longer, I’ve messed up too much meanwhile. And I will not repeat such a test!

What I did in detail:

I have a very big Collection “Schnellnotizen”.
Many Objects in it are tagged as “Knoten”.
I have also a Set called “Knoten (S)” that is also in the Collection “Schnellnotizen”. The Set grasps all Objects tagged as “Knoten”.

My attempt was, to move all these so tagged Objects out of the Collection “Schnellnotizen” into a new Collection “Knoten”.
I’ve thought it would be a smart move to simply transform the existing Set “Knoten (S)” in a Collection.
I’ve further thought, this new Collection would link only to Objects tagged as “Knoten” (this was the filter for the Set).
But in result of this transformation (Set into Collection) I got a Collection that links to some hundred totally irrelevant Objects and my Graph is now a pure chaos!

Additional Context

Using the history to undo this transformation and restoring the old Set didn’t solve the problem.
Now I have my old Set back, yes, but there are still these hundreds of unwanted connections in the Graph, leading to irrelevant Objects. :frowning:

I can’t see any way to undo the chaos, except deleting the Set and built it completely new from scratch . :frowning:

Also I don’t understand why this has happen?
What does the command “transform into Collection” do - or what is it supposed to do?

I not even see a way to “unlink” the unwanted Objects from the Set manually!
In the restored Set’s Flow is no option do unlink an Object from it. There is no right click menu or something else.
And in the Sets’s Grid does the right click menu not contain an “unlink” option.

The irrelevant Objects not even appear in the Set’s Grid - off course not, because the Set’s filter shows only Objects tagged as “Knoten” - the relevant ones.
How can I now disconnect / unlink the irrelevant Objects from that Set?

OS

Win 10

Anytype Version

0.42.4

Network Mode

AnySync

Technical Information

OS version: win32 x64 10.0.19045
App version: 0.42.4
Build number: build on 2024-08-14 14:52:25 +0000 UTC at #926fe517a6a07b59730087ca356da38292556697 (dirty)
Library version: v0.35.3
Anytype Identity: AAtt6aReARByswg2CbvZhveoJEEcnydfDu7U2VAkgJALsE7D
Analytics ID: 8a514008-4f5d-40d3-970f-a0d241b63af2
Device ID: 12D3KooWGqd6JSafCCcEwvnke5JAVgBNnuR9gGQeSBQ5HdUboWtG

When confused with sets and links, I find it easier to just recreate the set with the same settings then delete the old one. That might be quicker than trying to unlink hundreds of links.

Very good idea! :+1:
Why didn’t I think on it?

But I’m still interested why this has happend?

Same happened to me lately, after our discussion about organization and how the set only approach doesn’t give structure to the graph I thought why not trying to convert it in a collection and ended with a mess of interconnected links.

Hey @Code-Jack

I’ve updated the title of your topic and moved it to the bug reports section. This is definitely undesirable behavior that I’ve experienced myself, and I’d love to see it solved. When you have a moment, please fill in the new fields I added to your topic, and then we’ll forward this to the Go team.

Thank you!

Done, @Angelo

This report has been added to our issue tracker and received by the Development Team.