Creating Qualifiers Using Object Navigator

Zoom Window Out
Larger Text | Smaller Text
Hide Page Header
Show Expanding Text
Printable Version
Send Mail Feedback
Save Permalink URL

Navigation: TeamConnect Setup and Development > Enterprise Customization Help > Creating Custom Pages > Custom Fields > Field Types > Custom Object Field Type

Scroll Prev Top Next More

You can use Object Navigator to assist you in constructing the paths on either side of your qualifier expression for a custom field of type Custom Object. This allows you to rely on the internal structure of TeamConnect to guide you in identifying attributes, rather than having to type them.

While Object Navigator helps you construct a path, you must also make the correct selections and type literal text in the Qualifier field where appropriate. For example, the following qualifier is constructed using Object Navigator where necessary (currentPhaseType), while a specific value also had to be typed into the field (name.Validation):

Qualifier Example

To take advantage of this option, select the Add Path using Object Navigator check-box when defining the custom field, as shown in the following image.

Fields for Adding Paths Using Object Navigator

Even if you decide to use Object Navigator to assist you, you must understand the concepts outlined in the following sections:

•Qualifiers for Custom Object Fields

•Qualifier Syntax and Data Types

•Examples of Qualifiers for Custom Fields of the Type Custom Object

The following table describes the fields for adding paths to define data entry fields for custom fields of the type custom object.

Points To Remember

The following points are important to understand about using Object Navigator for defining qualifiers:

•You must begin paths by first selecting either this or container, depending on from which record your path must originate (see the Fields for Adding Paths Using Object Navigator table).

•You may not need to use Object Navigator for both sides of your expression. Often, you need to type the particular text or numeric value you may be looking for, such as a phase name or the tree position of a lookup item, on the right side of the expression.

•If both sides of the expression you need to write require you to build a path, you may need to click the Object Navigator icon twice—first to build one path and again to build the other path, one on each side of the operator.

•You must manually type an operator after adding the left side of the expression and before adding the right side of the expression. For details, see Data Types.

•When you build a path and click add, the path that you have created is added to the Qualifier field.

The following examples are typical expressions used in a Qualifier field for a custom field of type Custom Object. You can use these as models for your own qualifiers.

Examples of Qualifiers for Custom fields of the type Custom Object

What you want to do	Qualifier expression	What this expression says
Ensure that projects available for selection in the custom field and the record that contains the custom field have the same parent.	this.parent.primaryKey=container.parent.primaryKey	The primary key of the parent of the project record selected in the field equals the primary key of the parent of the record where the field is located.
Filter project records available in the custom field by their phase. Only those records whose current phase is Open can be selected in the field.	this.currentPhaseType.name=Open	The name of the current phase of the project record selected in the field equals Open.
In a record where there are two custom fields of the type Custom Object, and the records selected in these fields have a parent-child relationship, filter project records available in one field to only show children of the record selected in the other field.	this.parent.primaryKey=container.detailList(PAYM).detailObjfValueList(Feature).detailValueFID	The primary key of the parent record of the project record selected in the field equals the primary key of the project record selected in another field of type Custom Object in the same record.
Ensure that the projects available for selection in the custom field have the same person in a custom field of type Involved as the person identified in the contact-centric field of the record that contains the custom field.	this.detailList(CLAM).detailInvlValueList(ReportedBy).detailValue.contact.primaryKey=container.contact.primaryKey	The primary key of the contact who is identified in the ReportedBy custom field in the project record selected in the field equals the primary key of the contact who is selected in the contact-centric field in the record where this field is located.
Ensure that only projects with the specified default category are available for selection in the custom field.	this.defaultCategory.treePosition=CLAM_LIAB	The tree position of the default category of the project record selected in the field is CLAM_LIAB.
Ensure that only projects with a particular value selected in a custom field of type List are available for selection in the custom field.	this.detailList(CLAM_AUTO).detailObjeValueList(LossCode).detailValue=LOSS_ROOT_VDRE	The tree position of the item selected in a custom field in the record selected in the field is LOSS_ROOT_VDRE.
Ensure that projects available for selection in the custom field were created within the past 30 days.	this.createdOn<=TODAY30	The createdOn date of the record selected in the field is within 30 days of today or equal to today's date.
Ensure that projects available for selection in the custom field meet three conditions: •The parent of the project is the same as the parent of the record that contains the custom field. •The current phase is Litigation. •The default category is Auto.	this.parent.primaryKey=container.parent.primaryKey;this.currentPhaseType.name=Litigation;this.defaultCategory.treePosition=CLAM_AUTO	This qualifier contains three expressions, separated by semicolons (;). See the descriptions for similar expressions in this table.