After such a long time (sorry), I updated the script to copy data from excel spreadsheet to Revit Schedule. The updated script is available at:
http://bim.nichitecture.com/copyexcel.html
The evaluation version can be downloaded from the above link. The evaluation version has a limit of 25 cells that can be copied into Revit at a time. You can buy the utility with no restriction in the number of cells to copy (at the bottom of this post!)
The software currently supports 64 bit and 32bit windows environment for:
The cost of the licensed version of the software:
Single license cost is $2;
Site license cost for a firm with less than 10 employees is $10;
Site license cost for a firm with less than 50 employees is $25;
Site license cost for a firm with more than 50 employees is $50;
I copy and paste from my previous post:
The script works with both Microsoft Excel and Open Office.org Calc.
The script copies a bunch of cells (rows x columns) and pastes them into a revit schedule (contiguous rows x columns).
http://bim.nichitecture.com/copyexcel.html
The evaluation version can be downloaded from the above link. The evaluation version has a limit of 25 cells that can be copied into Revit at a time. You can buy the utility with no restriction in the number of cells to copy (at the bottom of this post!)
The software currently supports 64 bit and 32bit windows environment for:
- Revit Architecture 2009
- Revit Architecture 2010
- Revit Architecture 2011
- Revit Architecture 2012
- Revit Structure 2009
- Revit Structure 2010
- Revit Structure 2011
- Revit Structure 2012
- Revit MEP 2009
- Revit MEP 2010
- Revit MEP 2011
- Revit MEP 2012
The cost of the licensed version of the software:
Single license cost is $2;
Site license cost for a firm with less than 10 employees is $10;
Site license cost for a firm with less than 50 employees is $25;
Site license cost for a firm with more than 50 employees is $50;
I copy and paste from my previous post:
The script works with both Microsoft Excel and Open Office.org Calc.
The script copies a bunch of cells (rows x columns) and pastes them into a revit schedule (contiguous rows x columns).
- The script works well if all the fields in Revit schedule are EDITABLE. (A normal schedule has lots of ‘read-only’ fields like Family name, Area, etc where this script will fail.) The cells also need to be 'instance' driven cells (as compared to 'type' driven cells)
- The script does not create blank rows for data in Revit (yet). You need to create as many rows as you might need using this button in the Revit option bar before running the script.
3 comments:
How do you create a "blank" schedule in order to receive the pasted information? I am having a hard time understanding what type of schedule to set up, with what types of fields to prepare for the data entry. I understand they need to be instance driven and editable, but how to I get there?! Thanks
It is best to create a room schedule or a key schedule for this.
1. Create a room schedule with room name and number.
2. Then go to the schedule properties and click on fields and then click on "add parameter".
3. Create as many parameters as you want with "Text" as the Type of parameter. Ok out of all the windows.
4. When you get back to the schedule view, you can click on the "New" button on the ribbon above to create multiple rows.
5. these cells are instance driven and editable... (using room numbers in the script can give an error if u try to assign the same room number for two rooms...)
i hope this helps.
This was a helpful reply, thank you!
I am attempting to put our project specifications into a matrix, and schedules seem to be the best tool for this.
My idea was to make a separate schedule for each section of the spec. If a section of the spec is not used in the project, we would just take that schedule off the sheet, and leave the others.
I need 30-some-odd schedules, and am happy that Revit allows copy-pasting of schedules!
The main problem is that I cannot copy and paste my schedules over and over again with the same pre-defined fields because Revit does not like duplicate custom fields. It tells me I am "attempting an unsuppoted operation".
So far my resolution is to name each field beginning with the spec section #.
Any tips would be appreciated!
Post a Comment