# Copy linked levels to current view and rename ones on same level

**URL:** <https://forum.dynamobim.com/t/copy-linked-levels-to-current-view-and-rename-ones-on-same-level/53580>\
**Category:** Revit\
**Tags:** dynamo\
**Created:** [July 30, 2020, 8:34pm UTC](https://forum.dynamobim.com/t/copy-linked-levels-to-current-view-and-rename-ones-on-same-level/53580 "2020-07-30T20:34:54Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Nick\_Boyts](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/nick_boyts/32/76313_2.png) [@Nick\_Boyts](https://forum.dynamobim.com/u/Nick_Boyts)\
**Post date:** [January 9, 2023, 7:56pm UTC](https://forum.dynamobim.com/t/copy-linked-levels-to-current-view-and-rename-ones-on-same-level/53580/11 "2023-01-09T19:56:04Z")

</div>

I know this is a slightly different question but it’s hard to follow when you go back and forth between posts.

> [@Categories vs. Category.ByName Discrepancy in 2.13](https://forum.dynamobim.com/t/categories-vs-category-byname-discrepancy-in-2-13/77196):
>
> Hey there Dynamo community. I’m checking my company’s scripts to make sure they work in Revit 2023/Dynamo 2.13 and noticed this issue with specifying Categories using the Category.ByName node. Wondering if anyone has any insight on this. We specify Categories using the ByName approach for simplicity, ability to be in a code block, etc. We’re trying to grab the four Categories in the code block, but you can see in the Category.ByName preview list that 0 & 2 are actually grabbing the "Analytical …

The straight forward solution is to compare elevations and match names. It gets trickier when you have different elevations. What do you expect to happen when that happens?

---

_[View the full topic](https://forum.dynamobim.com/t/copy-linked-levels-to-current-view-and-rename-ones-on-same-level/53580)._