Skip to content

Known Issues and Workarounds

The 3.0.1 release of the Cost Insight Connect (also known as aP Connect) contains unresolved issues from prior versions of Cost Insight Connect (as described in the release notes for the version in which they were identified) and these newly identified issues:

  • Mapped Multiselect UDAs Require Value – Cost Insight Connect supports the use of multiselect UDAs, including the mapping of multiselect UDA values from PLM. However, if you set a multiselect UDA as a costing input and select the mapping rule Mapped from PLM when no value is set for the associated field in PLM, the component for which the value is missing will not to be processed.

    Workaround

    if you set a multiselect UDA as a costing input for a PLM field that may sometimes be empty, use the Default if No PLM Value mapping rule.

  • Results from a Single Job Split Across Multiple Emails – In 2023 R1, Cost Insight Connect introduced support of multiple mapped email recipients per components. Components are grouped in emails where recipient lists are identical. If email recipients are not identical, results will be split across multiple emails. For example, email addresses in a different order per component result in separate emails per component, or a component that has an email address that is not present for all other parts in batch will be represented in a separate email.

    Workaround

    To minimize the number of email notifications sent for a given job, use the same ordering for lists that contain the same email recipients.

  • Teamcenter PLM Write Limitation if Incompatible Data Type is Specified – If the data type of a Cost Insight Connect field you include in a PLM Write action is incompatible with the data type the field that is mapped to in Teamcenter, the PLM Write action will fail and item revision objects will remain checked out.

    For example, if you map a Cost Insight Connect field of data type Real to a Teamcenter field of data type Integer, the PLM Write action will fail and item revision objects for which the PLM Write action was attempted will remain checked out.

    Workaround

    Ensure that the data type of each mapped field in the Create a New or Edit Connector dialog is compatible with the Teamcenter data types for all mapped fields that you include in PLM Write actions.

  • Teamcenter Return Latest Revision Limitation – In 2023 R1, if you select the Return Latest Revision checkbox for a Teamcenter workflow, only the latest revision of each component that meets the query criteria will be analyzed. All revisions other than the latest will be returned and transitioned to an errored state.