Skip to main content

Choose a relationship type

First, choose objects to store carriers and producers.

Fill out the following field:

FieldWhat to select
Select Relationship TypeSelect a relationship type to determine how carrier and producer objects are associated.

Choose between two relationship types:

A related record is based on the concept of a one-to-many relationship. This means you can reference contacts that are direct children of the account, like accessing all producers under a carrier.

Example 1​

The Carrier table defines the type of object you're using to group producers by, like if you want to run a roster for a program and you plan to use the Account object.

The Producer table defines the type of object you're using for producers.

The reference field (Account ID) identifies which carrier's contacts you want to use, like pulling all contacts that are children of a carrier.

Related record relationshipA Carrier card, the Account object in Clearpath, has an Account ID field. A Producer card, the Contact object in Clearpath, lists Producer A, Producer B, and Producer C, each with its own Account ID field. Arrows run from each producer's Account ID to the carrier's Account ID, labeled Related record.CarrierAccount object in ClearpathAccount IDProducerContact object in ClearpathProducer AAccount IDProducer BAccount IDProducer CAccount IDRelated record

Example 2​

Related record exampleContact (Producer) points up to Account (Carrier) through its Account ID field. Seven sub-objects - Education, Training, Branch Locations, Designations, License, Non-Resident Licenses, and E&O Insurance - each point up to Contact.Account IDAccount(Carrier)Contact(Producer)EducationTrainingBranchLocationsDesignationsLicenseNon-ResidentLicensesE&OInsuranceSub-objects of Contact

About a junction object​

Based on the concept of a many-to-many relationship, a junction object makes it possible to link multiple rows in one table to multiple rows in another table. This selection will be most commonly used to generate rosters.

A common use case is to reference producers connected via an indirect grouping who aren't direct children of the carrier, like an object that relates the producer to the carrier object, such as the Producer Appointment object. This makes it possible to access producers linked to a specific program.

Example 1​

In this example, producer A is associated with multiple carriers. Producer B is associated with only one carrier.

Junction object relationshipThe Producer Appointment junction object has a Carrier parent field and a Producer child field, with three rows: Carrier A with Producer A, Carrier B with Producer A, and Carrier B with Producer B. Arrows link each row's carrier to the Carrier table, the Account object, and each row's producer to the Producer table, the Contact object. Producer A is linked to two carriers; Producer B to one.CarrierAccount objectCarrier ACarrier BProducerContact objectProducer AProducer BProducer AppointmentJunction objectCarrierParent fieldProducerChild fieldCarrier AProducer ACarrier BProducer ACarrier BProducer B

Example 2​

In this example, Producer Appointment is the junction object.

Junction object exampleProducer Appointment, the junction object, points up to Account or Carrier Network (Carrier) through its parent field, and has a two-way link down to Contact (Producer) through its child field. Seven sub-objects - Education, Training, Branch Locations, Designations, License, Non-Resident Licenses, and E&O Insurance - each point up to Contact.Parent fieldChild fieldAccount or Carrier Network(Carrier)Producer AppointmentJunction objectContact(Producer)EducationTrainingBranchLocationsDesignationsLicenseNon-ResidentLicensesE&OInsuranceSub-objects of Contact