# Transfer Project Standards

**URL:** <https://forum.dynamobim.com/t/transfer-project-standards/44975>\
**Category:** Share\
**Tags:** revit, dynamo\
**Created:** [December 31, 2019, 9:36pm UTC](https://forum.dynamobim.com/t/transfer-project-standards/44975 "2019-12-31T21:36:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dcmasten1](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/dcmasten1/32/52484_2.png) [@dcmasten1](https://forum.dynamobim.com/u/dcmasten1)\
**Post date:** [January 4, 2020, 3:48pm UTC](https://forum.dynamobim.com/t/transfer-project-standards/44975/2 "2020-01-04T15:48:47Z")

</div>

After some experimentation, I’ve found that this approach works really well specifically for the title of this topic - transferring project standards. As for copying views, schedules & sheets, well that doesn’t seem to work out nearly as good. And there’s the other obvious caveats; you actually have to link a project, know the element IDs and the project cannot be in template format. So with that, here’s the Rhythm approach:

 ![copy from doc_2020-01-04_08-17-55](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/6/9/690cde1d66ae8f75633589af3d926fc719fb8e19.png)  
Rhythm’s nodes also allow you to successfully search the parameters of an unopened document which means that filtering specific elements is not an issue. This also works for drafting views:  
 ![copy from doc_2020-01-04_12-40-56](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/7/c/7c294f7448267fed5624110f0a65f35ba4dd610a.png)

[Insert detail views from master details](https://forum.dynamobim.com/t/insert-detail-views-from-master-details/30303/2)  
[Copying schedules from other project](https://forum.dynamobim.com/t/copying-schedules-from-other-project/6772)

---

_[View the full topic](https://forum.dynamobim.com/t/transfer-project-standards/44975)._