Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.


Tips for Navigating Objects

This section provides tips for creating paths with Object Navigator and lists examples of common bridges and paths.

Practical Tips for Building Paths

  • The field label can help you determine which attribute to select. For example, the currentPhaseType attribute corresponds to the Current Phase field. However, there are two exceptions to this general rule:
    • The type-> attribute (instead of "role") represents project assignee roles in the JProjAssignee table.
    • The owner-> attribute (instead of "task" or "project") for task or project assignees (in the JProjAssignee and JTaskAssignee tables) identifies assignees for a task or project.
  • To create a path, you typically do not have to traverse more than one or two tables. If you have traversed over three tables and still cannot find the required attribute:
    • You may have selected the wrong bridge. If so, click back or cancel and start again. For assistance, check Object Model: Read This First.
    • The required attribute may not be accessible from the current object table. If so, you may have to write a Java action for the desired operation.
  • When constructing a path, make sure that the end of path value type matches the value type of the field whose value you are setting.
    For example, if you are setting a value for a number field and the path ends with a date, you cannot add the path. Or, if you are building a path that identifies a user, the end of path attribute must be in the YUser table.
  • In most cases, displayOrder, version, and primaryKey are not useful.
  • In certain screens, attributes with the suffix "List" cannot be traversed, so they are not displayed with an arrow (->). This indicates that the related table is not applicable.

Common Bridges and Bridge Attributes

  • The bridge attribute contact-> in the TProject table represents the contact selected for contact- centric custom objects.
  • Items that have the "List" suffix are bridges that typically link to sub-objects, such as a project's assignees.
  • To specify a user group, follow the path from the YUser table.
  • If you need to identify a field containing a system lookup table item, such as the field containing the role of a project assignee, your last selection in the path should be the bridge attribute type->. For example:
    • .assigneeList.type
    • .rightRelationList.type
    • .addressList.type
  • Custom fields created for an object can be reached by traversing the bridge detailList-> to the Category table, which links you to the list of all custom fields created for the selected category as shown in the following example:

See also the example of a complex path in Paths.

Commonly Used Paths

The following table lists the origins and destinations of common paths and the selections in Object Navigator used to build them. For more information on specific object model tables and attributes, see Object Model: Read This First.

Common Object Navigator Paths

From this object

To this attribute


Any T-table (any object)


Custom fields of the current object

  1. detailList-> (traverse)
  2. categoryName-> (traverse)
  3. customFieldName (ok)

A record's default category

defaultCategory-> (ok)

Any record category

  1. detailList-> (traverse)
  2. categoryName-> (ok)

The main assignee of a project that is selected in a custom field of type Custom Object

  1. detailList-> (traverse)
  2. categoryName-> (traverse)
  3. detailFieldName-> (traverse)
  4. mainAssignee-> (traverse)
  5. user-> (ok)

The user who created a record

createdBy-> (ok)



The total amount of an expense

totalAmount (ok)

The main assignee of a related project

  1. project-> (traverse)
  2. mainAssignee-> (traverse)
  3. user-> (ok)



The main assignee of a project identified in an invoice line item

  1. lineItemList-> (traverse)
  2. project-> (traverse)
  3. mainAssignee-> (traverse)
  4. user-> (ok)

The net total of a line item

  1. lineItemList-> (traverse)
  2. netTotal (ok)

The task category of a line item

  1. lineItemList-> (traverse)
  2. taskCategory-> (ok)

The expense category of a line item

  1. lineItemList-> (traverse)
  2. expenseCategory-> (ok)

The category of a vendor

  1. vendor-> (traverse)
  2. detailList-> (traverse)
  3. categoryName-> (ok)

The date of the invoice

invoiceDate (ok)

TProject (any custom object)


An assignee with a specific role

  1. assigneeList-> (traverse)
  2. <role>-> (ok)

A user assigned to a project with a specific role

  1. assigneeList-> (traverse)
  2. <role>-> (traverse)
  3. user-> (ok)

The current phase of a project

currentPhaseType-> (ok)

The user who is the project's main assignee

  1. mainAssignee-> (traverse)
  2. user-> (ok)

The role of a project's main assignee

  1. mainAssignee-> (traverse)
  2. type-> (ok)

The main contact of a contact-centric project

contact-> (ok)

Note: Only available when the custom object is contact-centric.

Custom fields of a parent project of the current object

  1. parent-> (traverse)
    Note: Only available when there is a parent- child relationship.
  2. detailList-> (traverse)
  3. categoryName-> (traverse)
  4. customFieldName (ok)    


The user's group membership

  1. groupMemberList-> (traverse)
  2. group-> (ok)

The user's default group

defaultGroup-> (ok)

  • Was this article helpful?