While I appreciate the script, wouldn't it be easier to just open an elevation/section and delete the levels you don't need? It just seems like overkill :hide:

Deleting the levels deletes the levels and the views. It doesnt delete the schedules and the sheets that had the views on them. And- since my template has 12 levels, with 9 areas per level, there are 750 sheets in the template.

Personally, i agree with you. I can zip through and delete all the sheets quite quickly. But i was asked (by a client) to put this together, so i did. =)

Cool. We have architectural and interiors departments who want quite different things from the template so rather than having to maintain multiple templates I'm looking into a Dynamo script that can be run from the playlist that will slim the template down from a master to one that only has views / templates / schedules etc that are relevant.

Are Dynamo packages any easier to deploy yet? Otherwise I'd prefer to see what I can do with the standard nodes.

Depends who you ask.

With the toolset im using (from Gordon Price: www.pragmaticpraxis.com) you can sync or mirror things to Roaming App Data at every users login, with ease. So- since the packages are currently being stored there: Yes, packages are quite easy to deploy.

If youre NOT using a tool like that, i would imagine it still sucks.

I used Archi-Lab from Grimshaw, for Archi-lab_Grimshaw.Selection.Select to use the "Get Level by Name" Node. Their might be something in the OOTB nodes that does this, and i just didnt find it. But i wanted to select a level based on a name, where the name was generated based on Integer Sliders. You might not need this at all.

I used Archi-Lab from Grimshaw, for Archi-lab_Grimshaw.Element Properties.Query to use his "String.Contains" Node. There ***IS*** a String.Contains in the OOTB nodes, and it DOES work fine. I had the lacing and conditions wrong. Before someone showed me how to do it, i found this node, which is much simpler.

I used SteamNodes.tool, to use the Tool.Eraser, for deleting items from the model. People were telling me there isnt a way to delete things without a custom node or a custom script. So either they were toying with me, or you need something custom here.

Those were the only custom bits i used.

Sure. Save the packages to a common folder (eve DropBox I bet) -- its an option when installing packages -- and point Dynamo to this folder. I think, unfortunately, that still needs to be done with the GUI.


Sent from my iPhone using Tapatalk

Gotcha. I didn't think about all the sheets...

For packages you can also create a Symlink to a network location in the folder where Dynamo expects the packages to be.
This could work if you want to avoid the GUI.
I did this for the older versions of Dynamo, before you could set the path, and each user just needs to run a .bat to set it up;

@ECHO OFF
@setlocal enableextensions
@setlocal enabledelayedexpansion




RD /S /Q "%USERPROFILE%\AppData\Roaming\Dynamo\0.8\packages "
MKLINK /D "%USERPROFILE%\AppData\Roaming\Dynamo\0.8\packages " "K:\Bim\Dynamo\Packages\0.8"

(Personally I like to pull the custom packages apart to see how they work and use the code directly, but thats just how I have learned everything technical)