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

Intralink 3.4 Instances being dropped for no apparent reason

Highlighted
Newbie

Intralink 3.4 Instances being dropped for no apparent reason

Hi,
We are experiencing what I call "dropped" instances in Intralink 3.4 for
an unkown reason. I define a "dropped" instance as an instance that
exists in the commonspace but DOES NOT EXIST in the LATEST version of
the generic. As one or more generics were checked in, the dropped
instance was not included. This can and does create a non-overrideable
check out conflicts.

I only know of two ways for this to occur, one is when a user deletes an
instance from the generic family table in Pro/E and then checks it the
generic and verified instances.

The second way involves checking in an out of date generic, with
instances, but this requires admin priviledges in our environment.

Seeing that the admin did not check in the generics and I believe the
user that they did not delete a row in the family table in Pro/E, how
then did instances get dropped


Question is, in Intralink 3.4, is there now another way to "drop" and
instance?


TIA,
Andrew Amsden

***** NOTICE *****
If you are not the intended recipient of this email, you are notified that disclosing, copying, distributing, or taking any action in reliance on the contents of this email and any files transmitted with it is strictly prohibited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify - or 1-800-MIDMARK (1-800-643-6275).
Announcements
LiveWorx Call For Papers Happening Now!