Relation does not update to the new type’s default template’s relations when changing types

Bug Reports Closed
1

What’s The Bug?

have a relation called ‘parent set’ For my default object type, notes, the parent set is the notes set. But when changing the notes type to another type where the relation ‘parent set’ is set to a different set, the parent set relation does not update. For example if I change the type to ‘entry’ where the parent set is in the default template is 'entries, the parent set remains 'notes.

How To Reproduce It

  1. Create an object relation that is filtered for the ‘set’ type. You could name it ‘parent set,’ as ! do with mine.
  2. Update the default templates of two object types to include that new relation. Ensure that the two object types have DIFFERENT sets chosen for each.
  3. Set one of those as the default type.
  4. Create new object.
  5. Change that new object from that default type to the other type you chose to use in step 1.
  6. Notice that the parent set relation doesn’t change. The set remains as the default type’s set and doesn’t update to the new type’s set.

The Expected Behavior

I want the default type’s set relation to update when changing to the type to match the chosen set of the new type.

Additional Context

This doesn’t only happen when changing the default type to another type, it also happens when changing any type to another type. Also! While we’re on it, the icon doesn’t change either when changing one type to another type whose default template’s icon is different.

Device

Macbook 13-inch, M1, 2020

OS

Sequoia 15.1.1

Anytype Version

0.42.5

Network Mode

AnySync

Technical Information

OS version: darwin arm64 15.1.1
App version: 0.45.2
Build number: build on 2025-02-13 11:57:09 +0000 UTC at #2c0826b346001f15fd0f9c720a83db8487e269a1 (dirty)
Library version: v0.39.10
Anytype Identity: A7JGAn8YT1NKSJaNSMMzsKCyxZvE6JW33nsax4z9VkndkrRC
Analytics ID: ae233490-9c4e-4e20-a986-0cc255483c70
Device ID: 12D3KooWBn9BjxvdRoGeiwHNCr6vzy1cN1RutDUrfficrAdazfp1

2

It would be nice if you shared a screen recording of the exact steps you’re taking, because if I’m understanding you correctly, then this shouldn’t be possible because Apply Template to an Existing Object hasn’t been implemented yet.

4

No, I wrote that wrong and have since edited the title. I meant that when you create an object, its default template is applied, and when you change that type, the default template of that second type is applied–or should be, but it isn’t applied properly set any relation that is an object relation filtered for set does not change. Recording:

5

The value of a relationship is not modified when a template (or type) is changed.
It is initiated only when the object is created.

In fact, this would run counter to a system that allows the template of several objects to be changed (like Apply Template to an Existing Object) : if these objects themselves have relations whose values have been updated, these values would be overwritten when we update or change template.

6

Bless your soul, Shampra! That’s perfectly explained!