# Clockwork ProjectPosition node

**URL:** <https://forum.dynamobim.com/t/clockwork-projectposition-node/73302>\
**Category:** Revit\
**Tags:** revit, clockwork, dynamo\
**Created:** [February 13, 2022, 4:39pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302 "2022-02-13T16:39:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Lindner](https://avatars.discourse-cdn.com/v4/letter/j/b38774/32.png) [@Jason\_Lindner](https://forum.dynamobim.com/u/Jason_Lindner)\
**Post date:** [February 13, 2022, 4:39pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302/1 "2022-02-13T16:39:25Z")

</div>

Greetings

I am trying to use this node Document.ProjectPosition in a script but it somehow always report nulls no mater how I position/reposition the project. Is there a secrete recipe to it?

Using Revit 2022 with Dynamo 2.12 Clockwork 2.3.0

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/2/9/290cb0f8a02749189d86dc71f367883cb05bfa85.png)

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [February 13, 2022, 6:35pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302/2 "2022-02-13T18:35:55Z")

</div>

I think this may be due to a change in the API in Revit 2022, both in terms of properties and units.

Open the custom node (double click on it), select everything in the node, close the node, paste it all into the workspace, and wire the inputs from the current custom node into the pasted inputs.

This will produce a meaningful warning on the Python node(s) which are creating the null results, and the community can give you some guidance from there.

---

<div class="post-metadata">

**Author:** ![Jason\_Lindner](https://avatars.discourse-cdn.com/v4/letter/j/b38774/32.png) [@Jason\_Lindner](https://forum.dynamobim.com/u/Jason_Lindner)\
**Post date:** [February 13, 2022, 7:39pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302/3 "2022-02-13T19:39:14Z")

</div>

Hi Jacob,  
Thank you for the reply…The error was in the second layer of custom nodes…and I think it is what you said…the units

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/d/1/d11253b8ef37464448a9cfd8728a29fb34255989.png)

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [February 13, 2022, 9:29pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302/4 "2022-02-13T21:29:40Z")

</div>

Yep, that class is gone in 2022.

> **[Revit API Docs](https://www.revitapidocs.com/2022/313c3c08-acf8-e629-2e65-37d3d08153b0.htm)**
>
> Online Documentation for Autodesk's Revit API: 2015, 2016, 2017, 2017.1, 2018

Sadly this is going to take a bit to put the puzzle back together. I’ll look into options next week.

---

<div class="post-metadata">

**Author:** ![Alban\_de\_Chasteigner](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/alban_de_chasteigner/32/39650_2.png) [@Alban\_de\_Chasteigner](https://forum.dynamobim.com/u/Alban_de_Chasteigner)\
**Post date:** [February 13, 2022, 9:36pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302/5 "2022-02-13T21:36:11Z")

</div>

Hi,  
You could use instead the _Get Project Locations_ node of the Genius Loci package instead.

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [February 13, 2022, 10:33pm UTC](https://forum.dynamobim.com/t/clockwork-projectposition-node/73302/6 "2022-02-13T22:33:38Z")

</div>

“Check Genius Loci to see if it’s got an alternative.” is high on my list of trouble shooting solutions for packages needing an update these days.

Well done as always @Alban_de_Chasteigner!  
🙂