# "Synced blocks" or "transclusion" with Headers, but not the way you want it 😄

**URL:** <https://community.fibery.io/t/synced-blocks-or-transclusion-with-headers-but-not-the-way-you-want-it/6032>\
**Category:** Bugs & Issues\
**Created:** [March 30, 2024, 4:03am UTC](https://community.fibery.io/t/synced-blocks-or-transclusion-with-headers-but-not-the-way-you-want-it/6032 "2024-03-30T04:03:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [March 30, 2024, 4:03am UTC](https://community.fibery.io/t/synced-blocks-or-transclusion-with-headers-but-not-the-way-you-want-it/6032/1 "2024-03-30T04:03:25Z")

</div>

I just discovered what I think is an unintentional “transclusion” or “synced blocks” (Notion term) feature, er issue. I copied an H3 and the bullet point contents below it from one page to another. Then on the source page I Collapsed the H3 and… to my surprise the H3 on the _destination_ page also collapsed! I didn’t realize what was happening at first so I expanded it, only to find (of course) the one on the source page got expanded as well. Then I copied the Anchor Links of each and, although they had different page “paths” in the URL, their IDs were the same, which probably explains this behavior. If it worked more fully and indicated a “synced block” (and let you navigate to other instances) I’d almost be tempted to call it a feature, but for now it’s a bug. 😉