What kind of objects are you talking about? And what is the link?
Some EPMDocument relationships are more difficult to delete than other relationships like WTPart to WTPartmaster usage links, or WTPart to WTDocument links.
For example, if a WTPart Number 123 version A.1 uses WTPartMaster 456, but WTPart Number 123 version A.2 does not use WTPartMaster 456, then you cannot delete all versions of WTPartMaster 456 because it is used by that earlier iteration of WTPart Number 123 A.1. In that case, you have 3 options.
1. Use life cycle state, and/or a naming or numbering convention, and/or access control rules by location to any version(s) of WTPartMaster 456 to "Cancelled" or whatever communicates that it is no good.
2. Delete Version A of WTPart Number 123 (or even just delete the Non-latest Iterations of Version A), at which point you can now delete all versions of WTPartMaster 456. This is the best approach in most cases.
3. Write a custom, administrative "Delete" utility, like we did, that allows you to delete parts like 456 in the example, above, by using an API that safely bypasses the "uses" restriction, and other restrictions. If you go this route, then you have to be very, very careful not to corrupt any data; and you always have to remember that there is no "undo delete" in Windchill.
Al
