Skip to main content
A
AP_110913234-Participant
4-Participant
September 9, 2024
Question

Visualisation Duplicating when Import existing CAD drawing

  • September 9, 2024
  • 1 reply
  • 606 views
I am using Windchill PDMLink Release 11.1 and Datecode with CPS M020-CPS14

We have two different Windchill servers of the same release (the second server is a full copy of the first one), and we use the Export/Import Utility to transfer information between them. When transferring CAD drawings that already exist in the target system, the CAD drawing is ignored (expected behavior), but the associated visualization is duplicated (not expected behavior) and set as the default representation. Thus, over time, too many visualizations associated with a drawing accumulate, and the export jar becomes too large. How can we adjust the system to ignore the visualization if the associated CAD drawing was ignored during Import?

    1 reply

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    September 9, 2024

    This article talks about filtering out visualization data but it specifically says that EPMDocument data cannot have visualization data filters.

    https://www.ptc.com/en/support/article/CS163360?source=search

    Recommend posting and idea to have this added as a feature. If its just CAD drawings, I might recommend a cleanup customization that you could run post import that would remove the duplicated representations and reset the previous to the default. Just out of curiosity, it is possible to republish those exactly in the target system. Are you confident that the results would be the same? That might offer you some new possibilities. 

    A
    AP_110913234-ParticipantAuthor
    4-Participant
    September 9, 2024

    Thanks for your reply!

     

    We cannot republish the documents in the target systems because the associated ECNs are not transferred, but information about them is shown in the exported visualization, and if we republish the documents this information will be lost.

    We discover that there is the UfidMapping table in the DB, where (if I understand correctly) the object's borth UFID (imported object's UFID from the source system) and local UFID (generated in the target system after import) are mapped. But for DerivedImage it does not work. May be there is the approach to adjust the Export/Import Utility (through some handlers may be) to create UFID mapping for the DerivedImage and ignore importing the visualization if its UFID is already contained in the table?

    Terms & ConditionsAccessibility statement