Describe the bug
When you create a custom type with some relations added, then you create a set, then you add a new relation to that type, that relation is invisible in the set created before. You can’t use it in filters, or display it in set view.
Steps to reproduce the behavior:
- Create a custom type.
- Add some relations to that type.
- Create an object of that type.
- Create a set of that type.
- Add a new number relation to the type.
- Return to the previously created set.
- Try to display the newly added relation or set a filter to it.
The newly added relation should appear in the set created before.
- OS: Windows 11
- Anytype Version: e.g. 0.21.9
@gcsapo Hi! Thank you for your notice! We haven’t implemented this yet, but plan to do that in the future
For future reference: there are two ways to add Relations to an Object:
- Add the Relation to the Object Type of your Object
a. You go to the Object Type of the Object
b. You add a new Relation to the Object Type (either existing or from scratch)
c. Create a new Object from the Object Type
d. Add a new Relation inside the Object
This way, the Relation is linked to the Object Type and therefore always available to be added to added to Objects of that Type AND available in Sets for that Object Type to be added as a column.
- Alternatively, you can add “ad-hoc” Relations to Objects
a. Open an existing or create a new Object of any Type
b. Use the “/” slash menu and select the option to add a new Relation
c. You can select an existing Relation to be added to the Object OR create a new Relation from scratch
Using this second method, the Relation is only linked to the Object, and therefore the Relation is NOT available to be selected as column in a Set of the Object Type of the Object you added the new Relation to.
@div3xi is this something we can explicitly add to the documentation? I think that will be helpful