Publishing to a ProjectWise Datasource

You can publish sheets and/or views from a Revit project file (RVT) to PDF or DWG.

In this example, let's assume that you want to:

• publish a few sheets from a Revit project file (RVT),
• and you want to publish them as PDF documents, stored in a ProjectWise datasource,
• and you want certain property values from the original Revit sheets to be copied over to the new documents in ProjectWise,
• and you want the new documents to be named using a combination of properties from the sheets they are published from,
• and you want a new version to be created, if a document of the same name already exists in the destination folder

First, configure your project like this:

1. Create an advanced integration project in the ProjectWise browser. (see Creating Revit Advanced Integration Projects)
2. In the project, create an environment mapping that maps certain Revit sheet properties to ProjectWise environment attributes. (see Configuring Attribute Mapping)
3. In the project, create a publish location with the following parameters:

   (see Adding Locations to Projects)

   1. Make sure the Role of this location is set to Publish Location.
   2. Make sure you bind this location to a work area or folder in ProjectWise that has an environment assigned to it. (see Adding Locations to Projects)
   3. Use the Mapping list to assign the environment mapping to this location. (see Configuring Attribute Mapping)
   4. Use the Name Template field to select which Revit sheet properties will be used to generate the names of the documents that get created using this location. (see Configuring a Name Template for a Location)

Then, use the configured publish location to publish sheets to PDF documents:

(see Publishing)

1. Open the Revit project file (RVT) you want to publish.
2. Open your advanced integration project in the ProjectWise browser.
3. Right-click your publish location and select Publish to PDF.
4. In the dialog that opens, select the sheets you want to publish and click OK.
5. If a document of the same name already exists in the destination folder, click Create Version when prompted.

Results:

• A PDF document for each selected sheet is created and stored in the ProjectWise work area or folder that is linked to the selected publish location.
• The environment attributes of the new ProjectWise documents are populated with the property values of the sheets they were published from, as determined by the environment mapping you configured and assigned to the publish location.
• The names of the new documents are generated using the combination of Revit sheet properties you included in the name template.
• If the destination folder already contains PDFs with the same name, a new version will be created for each PDF document.

  (If you have a PDF differencing tool installed, you can use it to compare the published versions at different stages of your project).

• If the ProjectWise destination work area or folder has a workflow assigned to it, the documents will be placed in the first workflow state of that work area or folder. This way, you can publish documents to the initial state with the ProjectWise work rules engine.

Publishing to the ProjectWise Share Portal

From a Revit advanced integration project, you can publish to the ProjectWise Share portal of the associated ProjectWise project in the CONNECT Center. This is the basic workflow:

1. In integrated Revit, create an advanced integration project and associate it to a ProjectWise project. (see Creating Revit Advanced Integration Projects)
2. In integrated Revit, in the advanced integration project, create a publish location and click the Share button to link this location to the ProjectWise Share portal within the associated ProjectWise project.

When you go to publish using this location, the published files will be stored in the ProjectWise Share portal within the associated ProjectWise project.

Sharing Data Using Links and Revit Model Publishing

Consider a situation where you have people in different offices working on different parts of same Revit project.

It could be reasonable to store the stable state of their work in a shared ProjectWise datasource.

For this, eTransmit functionality could be used. It will let you publish your part of the work to ProjectWise.

It will let people in other offices use it as a reference in their projects. They will just need to include the location where the stable state is published to an external content location and create the reference from inside of their working documents. It will allow you to have isolated 'Work in Progress' documents, but 'Shared' documents that are in an intermediate stable state.

Working with Revit Server and BIM 360 Design Central Files

If you are using Revit Server or BIM 360 Design, you can continue to host the Revit central models on Revit Server or BIM 360 Design, and then use the references from ProjectWise.

For this, you need to add and associate your central file to the advanced integration project (open the project file from Revit Server or BIM 360 Design as usual, then use the Add Current Document command in the ProjectWise browser to both add and associate the file to the advanced integration project - see Adding and Associating Revit Files to the Project).

When your Revit project file (RVT) is associated with the advanced integration project and added to the Work In Progress location in the project, it will be possible to resolve the references attached from ProjectWise using an external content location and the Link command on its items (for example, use the Link CAD command on a DWG file within the external content location).