Skip to main content
M
MarkFoose1-Visitor
1-Visitor
June 14, 2016
Question

possible to assign document as two different types

  • June 14, 2016
  • 1 reply
  • 1635 views

When adding documents to Windchill, a document type must be chosen.  This "type" designator controls how the document

can be associated tgp WTParts.  I have a need to associate a document to one WTPart as a "described by" document,

but to another WTPart as a "Reference" Document.  Is this possible? If so, how?

1 reply

B
bsindelar1-Visitor
1-Visitor
June 14, 2016

You may be referring to the fact that by default, only the WTDocument soft-type of "Reference Document" can use the "Reference Document Link" association type to a WTPart.

You can remove this restriction by changing the value of the preference called:

  • Part to Document Association Logic

The default value of "No", then you can ONLY use the "Reference Document" WTDocument type to make a reference document link to a WTPart and you also CANNOT use the "Reference Document" WTDocument type to make a described by document link to a WTPart.

If you change this property to "Yes", then any type of WTDocument can have either a described by or references link to WTPart.

If you have any other Windchill questions, feel free to e-mail me directly at robert.sindelar@eccellent.com.

    M
    22-Sapphire I
    MikeLockwood22-Sapphire I
    22-Sapphire I
    June 14, 2016

    Changing that preference eliminates some very valuable functionality and should only be done as a last resort in my humble opinion.  Worth really taking the time to understand what Describes and Reference links do.

    B
    bsindelar1-Visitor
    1-Visitor
    June 14, 2016

    Yes that is true.

    But given Mark's request, and since it is not possible for a WTDocument to be two different types of object simultaneously, and since the default value of the property I listed allows for only one or the other association to be used, this is the first thing I could think of to address this particular request.

    Can you explain what particular functionality would be lost using this property, for Mark and my benefit?

    Thank you.

    Terms & ConditionsAccessibility statement