My Oracle Support Banner

MCAD Connector Is Not Preventing Duplicate Design Number If the Number Already Exists in Agile (Doc ID 2729003.1)

Last updated on NOVEMBER 26, 2020

Applies to:

Oracle Agile PLM MCAD Connector - Version 3.6 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior

The MCAD connector for Creo is not preventing duplicate design Number, if the number already exists in Agile EC.

Expected Behavior

Connector should display warning message

Steps

  1. When assigning a design number (e.g.: TRAIL1) in "save preview" window and publish the model in Agile. It is successfully saved in Agile.
  2. Then again, in Creo try a save as of the part and assigned the same number (TRAIL1) and save it in Agile. The MCAD connector did not throw any error and the version rolled up to 2 for the Design object
  3. The MCAD connector should throw an error message for using the duplicate number instead of version rollup.

    In Agile Web client, if you try to do a save as for an object with an existing number, you will get an error message "Object Already exists in Agile"



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.