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

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

How to list nodes that differ between two baselines ?

GPI
6-Contributor
6-Contributor

How to list nodes that differ between two baselines ?

Hello,

We have started the evaluation of Windchill RV&S a few months ago, but we are stuck with an issue we met, so I come here to get some advices.

 

Here is the background :
We have a set of documents that belong to the same project.
They are versioned individually after some evolutions.
Finally, we create some baselines that gather some of these versioned documents.
The point is that we would like to list which nodes from these documents have changed between two baselines.
By "have changed", I mean "the values of some defined fields are not the same in the considered baselines".

 

We know it is possible to compare each document side by side to see the differences in their items for the selected baselines but it is not global and not usable as a list.

 

Here is a short example : let's consider only two documents DA and DB.
DA contains nodes : NA1 to NAx
DB contains nodes : NB1 to NBy
Document DA is updated and a new version is created : 1.0
Document DB is updated too and a new version is created : 1.0
Then We associate DA-1.0 and DB-1.0 the Baseline BL1.

Some time after, document DA is updated again some new versions are created, let's say 1.1, 1.2 and 1.3.
In the same way, document DB is updated once and new version 1.1 is created.
Then we associate DA-1.2 and DB-1.1 to Baseline BL2.

 

How could we retrieve in a smart way the following information with Windchill ?

Node doc version in BL1
doc version in BL2
Status BL1 to BL2
NA1 1.0 1.2 Updated
NA2 1.0 1.2 Unchanged
NA3 1.0 1.2 Deleted
... 1.0 1.2 ...
NAn 1.0 1.2 New
... 1.0 1.2 ...
NAx 1.0 1.2 Updated
NB1 1.0 1.1 Unchanged
NB2 1.0 1.1 Deleted
... 1.0 1.1 ...
NBz 1.0 1.1 New

Where the status could be based on some define fields (eg Text for this example)

  • Unchanged means that the fields are the same in the versions of the node applicable to BL1 and the version of the node applicable to BL2
  • Updated means that some defined fields are different for the versions node applicable to BL1 and BL2
  • New means the node exists in BL2 but not in BL1
  • Deleted means the node exists in BL1 but not in BL2

It does not seem to solve this with queries ; I assume it is possible do this with reports but I can't figure how...

 

Does anyone has some ideas ?

0 REPLIES 0
Top Tags