Announcement

Collapse
No announcement yet.

how to upgrade existing project to my new template?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    how to upgrade existing project to my new template?

    now can i make Revit to transfer my existing Building model to a new file with my new template... I used transfer project standards command but it didn´t seem to work properly ... For example i have custum annotation symbols in my template wich were not transferred into existing building model

    #2
    I do not believe that "Transfer Project Standards" transfers families. Only project settings (unit settings, line weights, object styles...) If you need to get families into your new project I believe you will have to load them by hand.

    Comment


      #3
      You can also copy and paste families from one project to another by way of the Project Browser. That way you could get all the families you want in one shot without having to load them one by one. Coping/pasting model geometry is a bit trickier but can be done if you set it up correctly.

      Comment


        #4
        Originally posted by renogreen View Post
        You can also copy and paste families from one project to another by way of the Project Browser. That way you could get all the families you want in one shot without having to load them one by one. Coping/pasting model geometry is a bit trickier but can be done if you set it up correctly.
        one can also select as many families as they like in the Load Family dialog with standard Windows selection tools. They need not be loaded one at a time unless of course they are in different folders. Then the PB copy/paste method is best
        I'm retired, if you don't like it, go around!

        Comment


          #5
          Open new project from new template,
          Link in existing project
          Select link and click "Bind". Bind all, including detail components and ungroup when finished.
          Martijn de Riet
          Professional Revit Consultant | Revit API Developer
          MdR Advies
          Planta1 Revit Online Consulting

          Comment


            #6
            Thanks for the process, Martijn. This worked for me on a resurrected project, except for one item: trying to avoid duplicate levels, I did not check the levels box while binding the link. The link's levels were different from the template, and items without levels lost their associations. I started over, making sure the levels in the template files matched the link, and resolved this issue.

            EDIT: In the link box, uncheck levels so duplicates are not created and the objects (mostly) map the the current project's levels instead.

            EDIT: As I've found out the hard way since, when you bind a link, all elements' "phase created" setting match the view that is current as the link is binded. This is obviously a problem with a multiple phase project. I was advised by my reseller to make separate links for each phase and bind them separately in phase-specific views to partially resolve this, but I can't recall how I resolved the "phase demolished" problem this creates for those elements that are modified during the course of the project. Sorry for the incomplete resolution, but I think some information is better than none here and that this trap is at least identified.
            Last edited by lost again again; June 27, 2014, 05:14 PM. Reason: added information (again).

            Comment


              #7
              I've come back to this page to process an old project that sat dormant while I've updated my template multiple times. I just noticed that all dimensions relevant to the grouped objects disappear upon converting the group to a link. This is a deal breaker for me, as some of those dimensions were placed to document the known and not so known dimensions used to create the original model. I NEED those dimensions. Other deleted dimensions define the scope of work, and I don't want to recreate all of them either.

              So I have to address this the opposite way: bringing all my new stuff into the old file. "Transfer Project Standards" only accomplishes some of the transfer. My redefined viewport, callout, elevation and section types did not come over.

              Following is the process I've worked out and successfully applied to the old project today (with notes at the bottom explaining some of the goofy steps taken):
              1. Reload families one by one (see Note #1 below): callout heads, elevation tag parts, section tag parts.
              2. Rename viewport types to old*. reload families one by one (see Note #2 below): view titles.
              3. "Transfer Project Standards" all except “project info", overwriting all.
              4. Callouts, elevations and sections don’t come over via TPS (see Note #3 below). extra steps to get these into original file (unresolved: what happens to view types that are replaced):
                • 4a. In a plan view of a project started from the current template, create one of each detail view type, elevation type and section type, copy to clipboard.
                • 4b. Paste into original file plan.
              5. Project browser: look for old* views and change type to current versions.
              6. Purge old view types from project.

              Notes:

              Note #1: Renamed the following one by one expecting the later copying and pasting of new view types to bring with them the related families, but no. Revit somehow insists on not bringing the related families but instead remapping all the view types back to the renamed families, despite any actual link being broken between the old and new families by the renaming.
              - viewport types, view title families.
              - system family callout tags, then callout heads.
              - system family detail view types; then callout tag types, section tag types; then callout head families, section head families and section tail families.
              - system family elevation types; then elevation tag types, callout tag types; then elevation mark families, callout head families.
              - system family section types; then callout tag types, section tag types; then callout head families, section head families, section tail families

              Note #2: Renaming view title families (but not viewport types) results in a similar illogical remapping of transferred viewport types back to renamed families.

              Note #3: Callouts, elevations and sections definitions and related families don’t transfer with TPS.

              Comment

              Related Topics

              Collapse

              Working...
              X