cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X

Translate the entire conversation x

Allocation of Part Instances

BF_13811900
13-Aquamarine

Allocation of Part Instances

Version: Windchill 13.0

 

Use Case: I am trying to include information within the context of a part instance that tells users where the part instances are allocated. But, I only want to show the parent part instances which the child is allocated to which are at a state of "Released". For example, I have part instance A which is a child of part instance B. Part instance B is at a state of "Released" at revision C. When I create a new revision of part instance B, the first iteration of revision D includes part instance A as a child within its structure. I can then remove part instance A from the structure of part instance B, revision D before setting the state of part instance B, revision D to "Released". If I then navigate to part instance A and look under the "Allocations" tab, part instance A is still said to be allocated to revision D of part instance B, despite part instance A not featuring in the structure of the released iteration of revision D of part instance B.


Description:

Is it possible to customize an information page to show all occurrences where my child part instance features in a "Released" parent instance?

ACCEPTED SOLUTION

Accepted Solutions
HelesicPetr
22-Sapphire II
(To:BF_13811900)

Hi @BF_13811900 

The point is that the HELLO points to the previous iteration of D revision so it points to the D.1 but the releasing version is D.2 where the HELLO part is not included. 

So this is how the system works.

 

PetrH

View solution in original post

4 REPLIES 4
Fadel
23-Emerald I
(To:BF_13811900)

can you add some screenshots 

Fede
BF_13811900
13-Aquamarine
(To:Fadel)

Hi Fede. Please see attached. Hopefully this makes sense?

HelesicPetr
22-Sapphire II
(To:BF_13811900)

Hi @BF_13811900 

The point is that the HELLO points to the previous iteration of D revision so it points to the D.1 but the releasing version is D.2 where the HELLO part is not included. 

So this is how the system works.

 

PetrH

Thanks very much @HelesicPetr !

Announcements
Top Tags