My Oracle Support Banner

Migrated .cfg Files Not Being Removed on Save (Doc ID 2216743.1)

Last updated on FEBRUARY 24, 2019

Applies to:

Oracle Agile PLM MCAD Connector - Version 3.3.0 to 3.5.0 [Release 3.3.0 to 3.5.0]
Information in this document applies to any platform.

Symptoms

On Agile PLM 9.3.5 with MCAD Connector  3.5.0 for Solid Edge Connector

On migrated data, when an assembly is loaded then checked-in, the old .cfg file is not getting removed. This results in the new renamed .cfg file and the old .cfg file being in the files tab of the Design and the attachments tab of the Item. See below screenshots :

This is the Assembly part with the .cfg file before reloading it from SolidEdge via the MCAD connector.

 

****************************************************************************************************************************

This is the same Assembly after being Checked -In again from SolidEdge via the MCAD connector. Notice that the migrated .cfg file didn’t get removed.


EXPECTED BEHAVIOR
-----------------------
the old cfg file (the existing ones)  should be removed after being renamed and checked in back again from SolidEdge.

Steps to Reproduce
-----------------------
The issue can be reproduced at will with the following steps:

  1.  Load to cad any migrated assembly into a blank workspace. Note the existing .cfg file on the Design and Item.
  2.  Make sure Item is on a CO to make check-in available.
  3.  Check in Assembly File
  4.  Compare the .cfg file on the new checked in version vs. what was noted in Step 1.



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.