Project Link Fields

This article describes the function and use of Project Link and Project Link List fields within the Customs Editor. These fields are used for linking from one project to another, using both one-way and two-way relations between projects. To learn how to add custom fields, including Project Link fields, read the article on using the Customs Editor.

Project Link fields enable a wide variety of complex relations between different projects. This article will go over each way that a project link field can be used. Project Link fields are used to relate multiple projects to each other and to enable limited nesting of data from one project in the reporting of another.

The Basics
Two-Way Relations in Static Sections
Two-Way Relations in Collections Sections
Reporting

The Basics

The simplest way to use project fields is a one-way relation, where a link to one project is placed within another project. Although linking a project within a project can be done through the built-in Related Section, a Project Link field allows reporting on specific data for the linked project that a Related Section does not. To view the reporting columns and criteria available for the linked project, jump to the reporting section.

A one-way project link will appear as a “search for a project” field and a plus button. You can fill this field by searching for an existing project in the field or clicking the plus button to add a new project. Optionally, you can specify what project type can be created with the plus button by using the “Limit to Project Type” option in the Customs Editor. Project Link fields look similar to Person fields in that they appear as cards, but clicking them will take you directly to the other project.

When adding a Project Link or Project Link List field in the Customs Editor, you will see an option to “Limit to Project Type,” “Link to Section,” and “Link to Field.” These options are not required and are primarily used for two-way relations, which are discussed below.

Project Links versus Project Link Lists

Project Link field allows only a single project link, while a Project Link list field allows for multiple projects to be linked. While a Project Link field appears as a single search bar with a plus, a Project Link List field appears similarly to a Multiple File Attachment field, with a “+ Add Project Link” link that will appear below any project have been added.

While both types of fields provide the ability to limit by reporting criteria in reports and to build two-way links, Project Link fields allow for nested data in reports, and can be used more easily in two-way links. Because of the limitations of Project Link List fields, in most cases Project Link fields will be more useful. 

Two-Way Relations in Static Sections

Project Link fields can also be connected in two-way relations. A two-way relation means that when one project is linked to a second project, the second project is then automatically linked back to the first project. A two-way relation establishes a relation between the two projects not unlike a foreign link in a relational database. This relation can be used to streamline especially complex template setups, Fusion exports, or API integrations. While potentially powerful, setup can be confusing and complicated. As such, Filevine support does not recommend using two-way links without the guidance of a Filevine consultant.

In static sections, two-way relations can be set up between two Project Link fields or between a Project Link field and a Project Link List field. A two-way relation cannot be created between two Project Link List fields. In static sections, the order in which the projects are connected does not matter, but order is important when creating two-way relations in collections sections. Read the next section to learn how to create two-way relations in collection sections. 

Setting up a two-way relation is a special process that requires an extra step. To set a two-way relation between projects using Project Link fields, follow the steps below. 

For the sake of clarity, the first project will be called “project A” and the second “project B.”

1. Create the first field. Create a Project Link or Project Link List field in any static section of project A. For more instructions on how to do this, consult the Customs Editor article. You do not need to specify any limits in the field in project A.
2. Create and specify the second field. Create a Project Link or Project Link List field in project B. Remember, two Project Link List fields cannot share a two-way relationship. When you create this field, click on the dropdown next to “Limit to Project Type” and select the project type of project A. In the subsequent dropdown field, choose the section and field name of the field you created in step one.
   
   
3. Choose project A. Go to the project and section of the field you created in step two in project B. In the search box, begin typing the name of the other project, project A. Choose the project.
4. Check the field in project A. Once you have added the project to one of the fields you have created, the other project will fill in automatically. You have created a two-way link!

Two-Way Relations in Collections Sections

Two-way relations in collection sections are similar to those in static sections, but when creating these two-way relations, the order in which the fields are created is important. Here are the important tips to remember when creating two-way relations in Collections Sections:

• Two collections sections cannot share a two-way relation. At least one section must be static.
• The field in the collections section must be added after the field in the static section. If the field is added in a collections section first, it will not be possible to specify that section when creating the second field, making the two-way link impossible.
• A Project Link List field must be created second. A two-way relation can be created for a Project Link List field that is created first, but any additional projects will not be able to be added to the Project Link List, rendering it useless as a list. 
• The project relation must be added in the project where the second field was made. The second created field should be specified in the Customs Editor, and the first field created should be added to the second one to create the link. 

Given these limitations, there are two ways to create two-way relations in collections sections. A Project Link field in a static section can be related to either a Project Link field in a collections section or to a Project Link List field in a collections section. These two options are described in further detail below.

Static Section Project Link to Collections Section Project Link

For the sake of clarity, we’ll call the first project “project A” and the second “project B.”

1. Create the first field. Create a Project Link field in any static section of project A. For more instructions on how to do this, consult the Customs Editor article. You do not need to specify any limits in the field in project A.
2. Create and specify the second field. Create a Project Link field in any collections section of project B. When you create this field, click on the dropdown next to “Limit to Project Type” and select the project type of project A. In the subsequent dropdown field, choose the section and field name of the field you created in step one.
   
3. Choose project A. Go to project B, and to the section and field you created in step two. In the search box, begin typing the name of the other project, project A. Choose the project.
4. View project A. Once you have added project A in the field in project B, you have the other project will fill automatically in project A.

Static Section Project Link to Collections Section Project Link List

For the sake of clarity, we’ll call the first project “project A” and the second “project B.”

1. Create the first field. Create a Project Link field in any static section of project A. For more instructions on how to do this, consult the Custom Editor article. You do not need to specify any limits in the field in project A.
2. Create and specify the second field. Create a Project Link List field in any collections section of project B. When you create this field, click on the dropdown next to “Limit to Project Type” and select the project type of project A. In the subsequent dropdown field, choose the section and field name of the field you created in step one.
3. Choose project A. Go to project B, and to the section and field you created in step two. In the search box, begin typing the name of the other project, project A. Choose the project.
4. View project A. Once you have added project A in the field in project B, project B will fill automatically in project A.

Reporting

Columns

Project Link fields are useful because, unlike projects listed in the Related Section, Project Link fields allow you to report on limited data from the nested project. If project B is linked in project A, reporting on project A can provide you with data on project B. Project Link List fields, in contrast, do not allow for nested data in a project. With a Project Link List field, you are able to report only on which projects are listed. 

The nested data that can be included as a report column through a Project Link field is as follows:

• Client (Last, First)
• Client Address 1
• Client Address 1 City
• Client Address 1 Line1
• Client Address 1 Line2
• Client Address 1 State
• Client Address 1 Zip
• Client Age
• Client Bar Number
• Client Company Name
• Client Created Date
• Client Date Of Birth
• Client Driver Lic #
• Client Email 1
• Client Fax
• Client Fiduciary
• Client First Name
• Client Full Name
• Client Gender
• Client Home Phone
• Client Is Minor
• Client Language
• Client Last Name
• Client Marital Status
• Client Middle Name
• Client Modified Date
• Client Nickname
• Client Notes
• Client Personal Mobile Phone
• Client Phone 1
• Client Remarket
• Client Salutation
• Client Specialty
• Client SSN
• Client Tax ID
• Client Texting Permitted
• Client Work Mobile Phone
• Client Work Phone
• Create Date
• Email Address
• Filevine URL
• First Primary
• Incident Date
• Office Phone
• Org Address 1
• Org Address 1 City
• Org Address 1 Line1
• Org Address 1 Line2
• Org Address 1 Name
• Org Address 1 State
• Org Address 1 Zip
• Org Email 1
• Org Fax
• Org Name
• Org Phone 1
• Other Phone
• Phase
• Project
• Project Number
• Project Type

Criteria

The exact reporting criteria available for Project Link fields and Project Link List fields is listed below.

For Project Link fields:

For Project Link List fields: