Understanding Aaron Maller's Placeholder Link Instructions

[ArchiN00B]

I have been trying to setup our company template and am using Aaron Maller's advice from the following location: http://malleristicrevitation.blogspot.com/2011/03/creating-revit-template.html

I see the value of what he is talking about under #12: Placeholder Links, but I don't quite get how it works.

So you setup dummy files with discipline-specific view settings, import consultant models into those dummy files by discipline, then link the dummy files into your project? So if that's the case, does this mean you copy a version of the blank dummy file into your project folder each time you need a new one? I'm confused because he writes "It doesn't matter where you store the files, you will never use them again"...

Any help and clarification much appreciated.

[Dimitri Harvalias]

What you do is use the Visibility/Graphics overrides in your template file to override the graphics settings of the links. In order to do this you need to have the links present in your template file.
What Aaron suggests is creating these links (one for each discipline you will be linking in), link them into your template and then set up views in your template to turn off grids, levels etc. in the linked file.
When you get models from other consultants you can re-path the links to point to your 'real' consultant files and the overrides you set in the dummy files will still remain.

[ArchiN00B]

Thank you Dimitri! The process is now eminently more clear. I will be implementing this into our template now!

[Simon.Whitbread]

...So you setup dummy files...
Yes, you are right up to this point. You create an 'arch.rvt' 'struct.rvt' 'mech.rvt' etc
They are blank files and they are linked to your project template. This allows you to setup View templates that include linked files.
When the Architect (or whoever) sends you their file, rather that linking it, you manage the current linked files in your new project (created from the template)
You can then select the 'arch.rvt' and 'reload from' which means you effectively replace the blank file with the 'real' one. Saves on a huge amount of set-up.

[ArchiN00B]

So then once the links and view templates are set up, can you delete the 'arch.rvt', 'struct.rvt' etc. files?

[ArchiN00B]

And should the dummy files be Central Model files, or just standalone files?

Update: Ok, so I just created 5 blank files; mechanical.rvt, structural.rvt, etc. and loaded them all into the project.

So I know I can override the graphic settings for these in each view individually ('Visibility Graphics' > 'Revit Links' > 'Display Settings' > click 'By Host View' > adjust the settings). But what happens when I am not using consultant models at all in the project? Are all 5 linked files going to show up in every new elevation, section, etc that I create? It seems like it would be a pain to have to hide those in each new view, especially on a project where I won't be using them at all.

So is there a global way to just hide the consultant models until I need them, while leaving them loaded in the template?

[Simon.Whitbread]

So then once the links and view templates are set up, can you delete the 'arch.rvt', 'struct.rvt' etc. files?

Ok, so the idea is that these 'placemarkers' are in your project template and your View Templates are created using these linked files. You don't actually link the consultants file, you use the 'Reload From' option so:

'arch.rvt' could become 'JoeBlowArchitectsInc.rvt' etc.

This wouldn't work if you linked the file as the View Template graphic override for linked files is referring to another file.



And should the dummy files be Central Model files, or just standalone files?

Standalone files - Purely for the sake of simplicity. If you are having to create View Templates that include a consultants workset visibility:
a. That would be on a project by project basis
b. You'll have my commiserations!


...But what happens when I am not using consultant models at all in the project? Are all 5 linked files going to show up in every new elevation, section, etc that I create? It seems like it would be a pain to have to hide those in each new view, especially on a project where I won't be using them at all.

So is there a global way to just hide the consultant models until I need them, while leaving them loaded in the template?

There's two options here:

i. Have the link files in an 'unloaded state' - Like an xref - it's attached, but the status is 'Not Loaded'
ii. Don't have any model objects in the dummy files

Or both, hope it helps

[ArchiN00B]

Thank you Simon. The "unload" command makes a lot of sense. I saw it there but it didn't occur to me. Also, the files I have created now are standalone files, so looks like I'm on the right track there!

As for the first issue you quoted, about deleting the dummy files, I'm not sure I got my point across. Let me try again:

I understand that you use "reload from" and point it toward the consultant's file without ever linking the consultant's file in. BUT, doesn't that mean I could delete the dummy files once they have been linked in the first time? I don't see why I would need 'structural.rvt' or 'mechanical.rvt' sitting on my hard drive since the links will be in place in the template...I mean, once they are deleted, worst case scenario is the filepath to the dummy file no longer works...but I never needed that filepath to work in the first place....as long as I can just use "reload from" and point it toward the consultant file, I shouldn't ever need the dummy files agian. Is that correct?

[Simon.Whitbread]

...I mean, once they are deleted, worst case scenario is the filepath to the dummy file no longer works...but I never needed that filepath to work in the first place....as long as I can just use "reload from" and point it toward the consultant file, I shouldn't ever need the dummy files agian. Is that correct?

I get your point and yes it would work, I just hadn't thought of it that way. The dummy links wouldn't be needed - but for MY piece of mind, I left them there... just in case :)

[Duncan Lithgow]

...but I never needed that filepath to work in the first place....as long as I can just use "reload from" and point it toward the consultant file, I shouldn't ever need the dummy files agian. Is that correct?

We do need the file paths to actually work in our Template because you can't change the visibility/graphics of a linked file if that file is not loaded. I assume I will be coming back to the Project Template to make improvements, so I keep the links at least easily accessible.