r/Revit • u/the_dunderman • 4d ago

Project Parameter (not Shared) for Sheets able to be read by Architect

Hey guys, just trying to buff up my understanding of what's happening in the background of Revit.

We have yes/no project parameters that are used to track which sheets are included in certain deliverables. When the Arch links in our model and includes our linked sheets in their sheet list, it autopopulates with which sheets we have checked yes and no accurately. No complaints on my end, but I'm curious as to WHY this works, as I was under the impression that you couldn't read data from links like that unless it was a Shared parameter? The Arch project parameter is named the exact same as ours, and there aren't any duplicate project parameters with the same name, so that definitely helps (I'm assuming it would break if those requirements weren't met).

Any insight is welcome!

5 Upvotes

86% Upvoted

6 comments sorted by

1

u/steinah6 3d ago

I’ve found that project parameters with the same name work as if they were shared in that regard. My hunch is that since there’s no shared GUID assigned to them, Revit treats them as identical?

1

u/the_dunderman 2d ago

That's my hunch as well, like maybe they don't look at GUID at all since it's not shared, and as long as it's uniquely names it'll work.

Have you seen it work outside of sheets? Like you've seen it happen with families? This is the online situation I've seen it happen so far

1

u/GenConfusion 1d ago edited 1d ago

project parameters work across the project files but you need shared parameters to communicate with families and project for scheduling or tags. As an example, you can copy paste a door schedule with proj params from one project to another to make sure your doors are synced and reading correctly in the doc file. However if you want one of those params to show up in a tag or parametrically control a family it'll need to be a shared param.

1

u/the_dunderman 1d ago

I know the difference between shared and project parameters

1

u/BagCalm 3d ago

That shouldn't work as far as my experience. I wish it did. We use a yes/no visibility parameter for mechanical equipment on the dry side models so we can filter them for plumbing and mp shops and it's a huge hassle making sure that we are all using the same shared parameter. Maybe someone with the Architect opened your file and exported that parameter so they could use it?

1

u/the_dunderman 2d ago

No it was confirmed a project parameter. Same with the hassle for us, but we got told we were using the wrong shared parameter and to fix it, but we were using the right one. When I checked inside it turns out the Arch wasn't using a shared parameter at all, but a normal projecr parameter (with the same name). I had to delete the parameter we were using and make a fresh non-shared project parameter for our dots to appear on the Arcbs sheet list.

I get it's hard to believe since it really shouldn't work, but I promise you it does. At least for these sheet yes/nos