We have all seen the Revit Warnings dialog and as you may already know, these can be ignored and the users can carry on with the tasks at hand but what does this mean for your project health! Some of these are problematic and ignoring the warnings is not really fixing the problem. I guess we should be mindful that if Revit sees fit to warn us of these issues then we should do something to resolve the problems. In the image below you can see a typical set of warnings in an average project. These can be a real headache for the BIM manager and in the following post I will outline a way of adding these errors to the model and then assigning users to ‘repair’ the problems.
The Revit Warning Dialog will allow the user to select elements but this can be extremely inefficient especially in large project where it can take a long time for Revit to open a view where the element can be located. This can be very frustrating for BIM technicians to wade through hundreds of errors, locate the elements and then try and fix the problems.
A Better Approach
On larger projects with multiple users we can utilise a simple Dynamo script to graphically show each error and allow the end users to see these errors in schedules, plans, sections, elevations etc and then isolate the errors and fix them or at least recheck the issue.
This is achieved by creating Shared Parameters to store the Revit Warning and comments on resolutions. You can then set up Revit filters to show each type of warning in different colours and do all the usual things such as isolating the elements, showing in different views and schedules.
In the example below you can see the Grids of Axis are shown in green, beam off axis are shown in yellow and walls in magenta. Also note the shared parameters storing the Revit warning in the elements.
The Dynamo Script
The Dynamo script is all based around the Bang package which can be downloaded by searching for the Bang package.
Add the GetWarnings node to a new dynamo session. You will also need to add a Boolean and set it to True to start reading the Revit Warnings.
The Warnings are then displayed in the top output and the list of elements in the lower output. It is a simple case of then setting a Revit Shared Parameter to store the value. In the image below I have created a Shared Parameter called ‘RevitWarning’, set it to Text and then used the Element.SetParameterByName node to write the warning text.
You can then set up some filters to display the warnings in views. I have also created a View Template that can easily be applied to any view to add the filters.
This is a simple and effective method of understanding where the warnings occur and then being able to assign these back to team members to resolve.
Hope this helps,