Skip to main content
HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
February 27, 2025
Solved

Experience with duplicity in EPMDocument table

  • February 27, 2025
  • 2 replies
  • 985 views

Version: Windchill 12.0

 

Use Case: The database table EPMDocument contains duplicity rows for revision-iteration object.


Description:

The database table EPMDocument contains duplicity rows for revision-iteration object.
For example object ABC has two records in the database for version B.1
First is latest second is not. Object is checked-in
I do not know the root case why there are duplicated records so I would like to know, if someone has similar experience.

System history shows the records correctly but method .istheLatestIteration can not work properly.

Query Report contains the duplicity

HelesicPetr_0-1740660090329.png

additional information this EPM Documents are created in Catia and saved by workgroup manager in Windchill

Thanks in advanced for any experience. 

PetrH

Best answer by d_graham

@HelesicPetr 

 

wrk-p is a private working copy. Different than a working copy. I’m sure you know this.

 

As for duplicity, I had a very strange situation years ago, Windchill 8.0. CAD Docs had duplicate primary application data. And there were a lot of them. No idea how this happened. The data had originally been migrated from Pro/I to v6.2.6 using the old Pro/INTRALINK Gateway. Then it had been upgraded to Windchill 8.0 a couple of years later.

To get ride of the duplicate ApplicationDatas I wrote a Java class that would delete the oldest one keeping only the newest one.

There were never more than two, no triplets.

 

Windchill worked fine before the cleanup but who needs duplicate primary content in their CAD data.

 

Not really the same thing as your seeing but I thought you might be interested in another duplicate story.😁

2 replies

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
February 27, 2025

Nothing I hate more than Windchill being duplicitous. Is this just one are are there more all over the place? What does the iteration history table look like from the UI for this object? Could it be that this is a working copy (checked out object)? Or possibly an uploaded modification in someone's workspace but not checked out? Are the branches the same ID?

    HelesicPetr
    22-Sapphire II
    HelesicPetr22-Sapphire IIAuthor
    22-Sapphire II
    February 27, 2025

    Hi @avillanueva 

    Funny thing is that the history tab looks like absolutely perfect. without any issue.

    The right row is shown in the history. But if I collect the objects by API I have problem to identify which one is correct one 😄 especially if the newer iteration exists 😄

     

    I found many duplicity records for many iterations and OOTB functions works ok because they use some mechanism that can filter the right iteration. 

     

    I am just curious if someone have seen this behavior. 

    I know that if user check-out the object then there are two rows for one iteration workingcopy/checkout copy but in this situation no objects are checkouted. 

    PetrH

    D
    18-Opal
    d_graham18-Opal
    18-Opal
    February 27, 2025

    @HelesicPetr 

    I noticed that the idA2A2 of B.1 where latest is true is a larger number than where latest is false. That’s the good news.

     

    What does the checkout info look like where idA2A2 = 165414290?

    HelesicPetr
    22-Sapphire II
    HelesicPetr22-Sapphire IIAuthor
    22-Sapphire II
    February 27, 2025

    Hi @d_graham 

    the check out info is very interesting. All duplicated records has the getCheckoutInfo value "wrk-p" even though the object is checked-in.

    Your hint is very useful. Thanks that I know how to filter this records. 

     

    In other hand I would really like to know if someone knows what case described issue. 

     

    PetrH

    D
    18-Opal
    d_graham18-OpalAnswer
    18-Opal
    February 27, 2025

    @HelesicPetr 

     

    wrk-p is a private working copy. Different than a working copy. I’m sure you know this.

     

    As for duplicity, I had a very strange situation years ago, Windchill 8.0. CAD Docs had duplicate primary application data. And there were a lot of them. No idea how this happened. The data had originally been migrated from Pro/I to v6.2.6 using the old Pro/INTRALINK Gateway. Then it had been upgraded to Windchill 8.0 a couple of years later.

    To get ride of the duplicate ApplicationDatas I wrote a Java class that would delete the oldest one keeping only the newest one.

    There were never more than two, no triplets.

     

    Windchill worked fine before the cleanup but who needs duplicate primary content in their CAD data.

     

    Not really the same thing as your seeing but I thought you might be interested in another duplicate story.😁

      Terms & ConditionsAccessibility statement