Friday, February 24, 2017

Export All Possible Revit Warnings

A few weeks ago, Konrad Sobon, posted a Python script for exporting all the possible Revit warnings to use in a Dynamo script that analyzes and ranks the warnings in the current model. Since I mostly work in C#, I took his Python script and created a C# macro. I've had several requests for it, so here it is...

public void ExportWarnings()
        using (StreamWriter writer = new StreamWriter(@"C:\temp\warnings.txt"))
            FailureDefinitionRegistry failures = Autodesk.Revit.ApplicationServices.Application.GetFailureDefinitionRegistry();
            IList<FailureDefinitionAccessor> failuresList = failures.ListAllFailureDefinitions();
            foreach (FailureDefinitionAccessor failure in failuresList)
                if (failure.GetSeverity() == FailureSeverity.Warning)

And the resulting file from Revit 2017 : Warnings.txt

Wednesday, February 01, 2017

Adding Revisions to a Sheet Index

Recently, I had someone make a request for adding an X to a column in a sheet index schedule for all the revisions that sheet had. Currently, they have to do it by hand and it is tedious.

To get this to work, I added a parameter for each revision called "Seq #" (with # being the revision sequence number). I looped through each revision on each sheet and looked up it's sequence number, then add an X to the parameter matching it.

Here is a video showing how it fills in the sheet index schedule:

And the code...

public void SheetRevisions()
 Document doc = this.ActiveUIDocument.Document;
 using (Transaction t = new Transaction(doc, "Revisions on Sheet"))
  // loop through all the sheets in the model
  foreach (ViewSheet vs in new FilteredElementCollector(doc).OfClass(typeof(ViewSheet)))
   // get a list of all the Revision Ids for this sheet
   IList<ElementId> revIds = vs.GetAllRevisionIds();
   // if at least 1 Revision, continue
   if (revIds.Count > 0)
    // loop through each of the Revision Ids
    foreach (ElementId eid in revIds)
     // get the actual Revision element
     Element elem = doc.GetElement(eid);
     Revision rev = elem as Revision;
     // add an X to the parameter named "Seq #"
     vs.LookupParameter("Seq " + rev.SequenceNumber.ToString()).Set("X");

Monday, May 02, 2016

RevitLookup 2017

I have compiled the latest source code for RevitLookup 2017 from Jeremy Tammik's GitHub (

Note: I did not create or edit this Revit Addin. I am only compiling it for those that don't understand or want to compile it for themselves.

Here is the download link:

It is also listed on the right-hand column under downloads.

Wednesday, March 16, 2016

PDQ Deploy and Inventory for Autodesk and other applications

I have been using PDQ Deploy and Inventory for about 2 years now. It has been one of the highest ROIs on a product I have ever used. The ease, speed, and reliability of being able to push a product, product updates, and custom product settings out to 350+ PCs from a $1000 pair of tools has been a game changer for my company.

What is PDQ?

PDQ Deploy and PDQ Inventory (by Admin Arsenal) are a pair of applications that allow BIM Mangers, IT Admins, etc to deploy software and files silently across many PCs as well as keep an inventory of all the PCs software, hardware, and more. The programs do not require any pre-installation of software on the PCs and can install just about anything most companies need across a single office or multiple offices.

My Setup

My company currently uses PDQ to inventory well over 400 PCs and pushes deployments across 7 offices in 2 countries. We use PDQ inventory to track which PCs have which versions and service packs of all software applications, then use PDQ Deployment to automatically push updates to them. We also use PDQ to push out new versions of applications as they become available. Lastly, we use PDQ to deploy suites of applications to new systems within the company, gone are the old days of having a system image with everything installed.

PDQ Inventory

PDQ Inventory can tie into your Active Directory (AD) to quickly learn about all of the PCs within your company. My company has PCs in an AD container system like in the image below. By having PCs grouped based on office and whether it is a desktop/laptop/conference room/server, allows us to only inventory the PCs we want to use for deployments. We do not currently use PDQ Inventory or Deploy for servers.

PDQ Inventory is used to create reports about which systems have which software as well as the version of the software. These reports are easy to build using the built-in report creator.

PDQ Inventory also has what are called “collections”. The collections are live reports of PCs that meet the criteria of the collection. For instance in the next image, it shows all the PCs that have an Autodesk product installed, then the PCs that have Revit 2016 installed, and finally the PCs in each office that have Revit 2016 installed. These collections can be used as a source of PCs that PDQ Deployment can use to deploy a package to.

PDQ Deploy

PDQ Deploy allows you to create packages of applications, patches, and settings than you can then push remotely and silently to any number of PCs.

Creating a package in PDQ Deploy is as easy as specifying the msi, exe, bat, etc file that you want to deploy. By combing several steps (see image) you end up with a full blown package like the image below for Revit 2016, Dynamo, several addins, ini files and updates.

Once you have a package built, you choose the PCs to push the package to. This can be from Active Directory, from a collection in PDQ Inventory, or even from a text file. We typically push out to about 10 PCs at a time. For PCs in other offices, we use a DFSR share to replicate all of the installation files to each office. Then the packages use a DFS namespace that is identical in each office to do the install from.

Here is the output for a package that installs AutoCAD Architecture 2016 (w/ SPs and hotfixes), uninstalls all pre-2015 Autodesk software on the PC, installs Revit 2016 (w/ addins, updates, ini files, etc), and Bluebeam PDF.


There are lots of other features that I won't touch on that include scheduling, automatic (start install when computer comes on), pre-made packages, and lots more.

The pair of applications have saved us countless hours for deploying software that the savings are probably immeasurable. If you want to try this out, the company has trial versions available. And if you have more questions about how we use it, please feel free to leave a comment.

Tuesday, April 21, 2015

RevitLookup for Revit 2016

With Revit 2016 officially out, I am working on updating my addins for 2016. One of the most invaluable addins has already been updated. Per Jeremy Tammik on his website,, RevitLookup has been updated for Revit 2016.

You can get the source code here: and build it yourself.

Or you can download a zip with a version that I have already built here:

Just extract the contents of the zip file into your Revit 2016 addins folder ( C:\ProgramData\Autodesk\Revit\Addins\2016\ )