In 10.2 M030 CPS24, You are unable to purge or delete an iteration because a branch point was created referencing that iteration when a new version was created.This makes it very difficult to cleanup bad data & vault problems. Reference TPI 147792, CS18659, SPR 2115294.
Hi Wayne, other Readers,
It looks like this is as designed due to Windchill's architecture. When a new version is created (i.e., the Revise operation), the iteration from which the new version was created becomes the "anchor" of the new version and its sequence of iterations. That anchor is called a "branch point", and it serves to position the new version within the overall version sequence of the Master. Windchill cannot allow a branch point to be deleted, unless the version that was created from it is also deleted. Otherwise, the integrity of the version sequence would be lost. Note that this limitation does not prevent any non-branch point iterations from being deleted.
Regarding bad data & vault problems, This would be one of the downsides here. Naturally you expected that the data was "not bad" when it was used to be revised into the later revisions, however if it was not, it might be wise to confirm ones made after the branch from the now corrupt data is actually not corrupt itself.
This would be a very beneficial addition when trying to clean up as the OP mentioned. An API method to move a branch point in order to perform cleanup operations is required for administrative purposes. Currently the setup is assuming users never make mistakes. Anyone working in the business is painfully aware this is not the case. Without this capability it is nearly impossible to break bad links or be able to delete something that gets tangled into the system with the spiderweb of links.
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.