7.0 or 6.1 template?

[Les Therrien]

Is it better to simply open my TEMPLATE file (61.) with 7.0 then save it?

Or should I use the 7.0 template and transfer all my data from the 6.1 template?

I always wonder about this when new versions come out.

[ita]

I believe I saw a batch conversion app for 6.0 . . . quite some time ago. Is there one avalable for 7.0?

[Steven Campbell]

There are a tons of small tweaks made to the 7.0 templates, mostly minor. Some of the changes include how structural walls work, view ranges for structural views tweaked, added a monolithic stair, set default materials for massing, reloaded all hosted families to cut correctly with new wall improvements, reloaded all family to make sure they were the latest versions, stacked wall added, added some default sun and shadow settings, etc.... There are too many to list and there can vary slight depending on the template (default, structural,...).

My recommendation is keep a list of tweaks made to your office template so you could quickly replicate it from the latest Revit default template. Re-save all your family file to the latest version and reload. Use copy paste or transfer project standards to move your custom system families to the new template.

Hope this helps

Steven Campbell
Autodesk Revit

[bclarch]

There are.......
....new template.

Hope this helps

Steven Campbell
Autodesk Revit
Yes it does. Thanks.

[Les Therrien]

thanks Steven

[Damo]

....Use copy paste or transfer project standards to move your custom system families to the new template. Thanks Steven, Just about to go through this as you post. Timely and appreciated.

[Scott D Davis]

Maybe the Revit team should consider a migration tool, that could take a 6.1 template, and do the transfer of standards for us. Maybe open a 6.1 template, and upon the upgrade, it prompts if you want all standards transferred to the new 7.0 template.

[Steven Campbell]

Maybe the Revit team should consider a migration tool, that could take a 6.1 template, and do the transfer of standards for us. Maybe open a 6.1 template, and upon the upgrade, it prompts if you want all standards transferred to the new 7.0 template.
I will make a formal customer request for this tool, I believe it already has been request from the development side. Besides when Scott makes a request we all jump to make it happen... j/k

Steve

[Wes Macaulay]

Thanks for the heads up, Steven. Very good to know.

[Scott D Davis]

Besides when Scott makes a request we all jump to make it happen...
Damn, that's good to know!!!! Didn't realize I had so much pull.......:p

Baseball's over, Red Sox won, now get back to work on 8.0!!!! :shock:

[christie.landry]

Baseball's over, Red Sox won, now get back to work on 8.0!!!! :shock:


I'm just going to be happy about getting a full nights sleep!

[kimheaver]

Use copy paste or transfer project standards to move your custom system families to the new template.

I ran transfer project standards to copy from my 6.1 template to a new 7.0 template, I checked copy everything. As a double check I ran it again with walls checked and it gave me the message "the following types exist in the destination project but are different" for the ones that I've altered.

If I repeat the process and allow it to overwrite, why does it show the same message that the incoming materials are different each time.


Regards,
Kim Heaver

[Les Therrien]

?????????????????

[bclarch]

If I repeat the process and allow it to overwrite, why does it show the same message that the incoming materials are different each time.
Because the 6.1 template remains unchanged while the 7.0 template contains all of the updated types. Therefore, after the first transfer, the transfer process always involves a 6.1 type (incoming from 6.1 template) being compared to a 7.0 type (already updated and now existing in 7.0 template). The program will, and should, always recognize these as different versions since one is already updated and the other is not.

[kimheaver]

Therefore, after the first transfer, the transfer process always involves a 6.1 type (incoming from 6.1 template) being compared to a 7.0 type (already updated and now existing in 7.0 template).

Ah ha, it makes sense now.

Thanks,
Kim

[PeterJ]

I have been struggling with this, but I'm about to start a couple of new jobs so it becomes key to what I am doing.....

The default UK template appears to be a 6.1 file as each time I start a new project using it I am advised that the project is being updated to a current version. Can anyone shine any light on this, please.

[rhys]

I have been struggling with this, but I'm about to start a couple of new jobs so it becomes key to what I am doing.....

The default UK template appears to be a 6.1 file as each time I start a new project using it I am advised that the project is being updated to a current version. Can anyone shine any light on this, please.
Same here but downloading the new build together with the GB template seemed to sort this out. The new template has things like stacked walls etc.

[Chad Smith]

Les, there are problems still occurring with upgrading families from 6.1 to 7.0, I know I've had my fair share, which by the way still aren't resolved, but hopefully soon.
So I would tread carefully when doing so.

[Les Therrien]

I've been so busy, I really haven't had the fortune to play with 7.0
I usually wait about a month or so before jumping into a new release.

[ctc]

Maybe the Revit team should consider a migration tool, that could take a 6.1 template, and do the transfer of standards for us. Maybe open a 6.1 template, and upon the upgrade, it prompts if you want all standards transferred to the new 7.0 template.

A migration tool would be even more useful if it also transferred the following.

If you have populated your template with all of the standard views that you might use for each level in a typical project : floor plans, ceiling plans, site plans, elevations, sections, isometrics; for each of the different disciplines: architectural, demolition, structural, electrical, plumbing, HVAC, finishes, landscaping; each appearing in the appropriate phase: existing or new construction, This could total 50 views! That's a lot of work to set it up from scratch manually.

Additionally, if your practice has adopted a sheet naming convention which remains the same across your different projects, [such as the AIA guidelines for sheet numbering] you can also have these transferred. This could total another 40-50 items! That's a lot of work to set it up from scratch manually.

[k.armstrong]

CRAIG - your are absolutley SPOT ON the mark!!!

As i understand (new user) one of the beautiful things with revit is you continue to refine your template as you do projects and thus as you have all the standard views set up and numbered (including schedules etc i guess) then you start drawing and revit takes care of creating the "reports" (ie pretty drawings, construction docs etc) to show the client/builder whomever.

So it does seem very sensible to have some migration tool that upgraded your existing template including views, sheets, schedules structure to the latest version - of course there might be quite a few questions to ask during the process and you would want a backup copy also

my 0.02 worth

Ken