<otherComponent> Element (for query or table source)

This element specifies an other component against which part entries must match.

Note

This feature is available in Acuit Pinpoint Workstation version 7.13 or later.

Parent Elements

otherComponents

Attributes

Name	Type	Description	Required
componentTypeName	string	The component type name of the other component.	Yes
componentModelNumColumn	string	The name of the column that contains model numbers of the other component. This corresponds to the componentModelNum attribute in otherComponent.	No
componentSerialNumColumn	string	The name of the column that contains serial numbers of the other component. This corresponds to the componentSerialNum attribute in otherComponent.	No

Child Elements

None.

Remarks

As these values are retrieved from the source rows, if both values retrieved for componentModelNumColumn (if specified) and componentSerialNumColumn (if specified) are blank, then no "other component" entry for this other component type will be added for this part entry; it will be as if no otherComponent has been added for this componentTypeName), so no check against this other component will occur for this parts list row. To require that a valid component of this type exists, at least one of the columns must contain some value (e.g., *).

For example, consider this component type configuration and source table:

Configuration:

<componentType name="Motor Program">
  <partsFromTable table="Motor Programs" unitModelNumColumn="Unit" componentModelNumColumn="Motor Program">
    <otherComponents>
      <otherComponent componentTypeName="Motor" componentModelNumColumn="Motor" />
    </otherComponents>
  </partsFromTable>
</componentType>

"Motor Programs" table:

Unit	Motor	Motor Program
UNITMODEL1	MOTOR1	PROGRAM1-1
UNITMODEL1	MOTOR2	PROGRAM1-2
UNITMODEL2		PROGRAM2
UNITMODEL3	*	PROGRAM3

Since the last row in the table as no value for the other "Motor" component, that component will not be checked when matching that part row. This results in these Motor Program scans being accepted for various combinations of unit and Motor model numbers:

	Motor: valid not installed	Motor: MOTOR1	Motor: MOTOR2	Motor: MOTOR3
Unit: UNITMODEL1	Motor Program: nothing accepted	Motor Program: PROGRAM1-1	Motor Program: PROGRAM1-2	Motor Program: nothing accepted
Unit: UNITMODEL2	Motor Program: PROGRAM2	Motor Program: PROGRAM2	Motor Program: PROGRAM2	Motor Program: PROGRAM2
Unit: UNITMODEL3	Motor Program: nothing accepted	Motor Program: PROGRAM3	Motor Program: PROGRAM3	Motor Program: PROGRAM3

Note that typically both of the associated component types will be configured from a common table, where the table explicitly lists all valid component combinations. For example, the above example would typically be configured like this instead:

Configuration:

<componentType name="Motor">
  <partsFromTable table="Components" unitModelNumColumn="Unit" componentModelNumColumn="Motor" />
</componentType>
<componentType name="Motor Program">
  <partsFromTable table="Components" unitModelNumColumn="Unit" componentModelNumColumn="Motor Program">
    <otherComponents>
      <otherComponent componentTypeName="Motor" componentModelNumColumn="Motor" />
    </otherComponents>
  </partsFromTable>
</componentType>

"Components" table:

Unit	Motor	Motor Program
UNITMODEL1	MOTOR1	PROGRAM1-1
UNITMODEL1	MOTOR2	PROGRAM1-2
UNITMODEL2	MOTOR2	PROGRAM2
UNITMODEL3	MOTOR3	PROGRAM3

This would result in the same behavior as detailed in the first example, except that the invalid unit/Motor combinations would not be allowed in the first place:

	Motor: valid not installed	Motor: MOTOR1	Motor: MOTOR2	Motor: MOTOR3
Unit: UNITMODEL1	Motor Program: nothing accepted	Motor Program: PROGRAM1-1	Motor Program: PROGRAM1-2	n/a
Unit: UNITMODEL2	Motor Program: nothing accepted	n/a	Motor Program: PROGRAM2	n/a
Unit: UNITMODEL3	Motor Program: nothing accepted	n/a	n/a	Motor Program: PROGRAM3