How to find view only relationships ?

Are you asking about Parts relationships? OOTB relationships of Parts that just for view only is Changes, to retrieve changes data you can use AML from the post you have comment. If you are asking general question, here how you can analyze if the relationship is for view purpose:

• If relationship is not related
• If Relationship (In TOC navigate to Administration->Relationships) under "Relationship View" tab you have some row that point to "outside" html or grid or form

Each solution use it's own logic how to store data - so there is no single answer    

Hi , Thanks for reply . I was asking general question. And your answer solved my problem for view only relationships. But there are some relationships where related_id is not mentioned still we can create and fetch those relationships. For example: CADFiles. Can you please help me to figure out what is the type of related objects to fetch when related_id is not given in Relationships. Actually I am using Java code to fetch these relationships. Thanks! -Ketan.

for the "CAD Files" example, you can fetch the "CAD Files" relationships => this is a null relationships which means that we just attach a relationship object without related for the "Changes" example, you cannot just fetch the relationship because here the relationship has just been created to show a tab in the Part form. What you see is actually a view which you can find in a script page in your install folder : Innovator\Client\Solutions\PLM\scripts\Changes Zahar gave the right tips to find out which relationship is actually used as a real "Null Relationship" and which relationships are actually just used as a tab. (Thx Zahar for the very quick answer !)

Hi Yoann, Thanks for reply ! -Ketan.

Hi Yoann, Can you please elaborate more on the null relationships ? What is the use case for just attaching a relationships to source object and not having related object ? Thanks ! -Ketan

Sure, A good example, is the native datamodel for Part, Part Document, Part BOM and Part instances Part is an Itemtype :

• It has a "Classic" Relationships to the Document itemtype. the relationship is called "Part Document". A document can be defined independently from the Part.
• It has an "Almost Classic" Relationship to the Part (itself) itemtype. The relationship is called "Part BOM". Parts can be created independently and then related in the Recursive BOM.

If you look at the "Part BOM" Itemtype (yes relationships also are itemtypes !) it has a null relationship called "Part Instance". A part instance cannot be independant from a Part BOM it is a more precise granularity of the BOM relationship and it tipically contains postionning of the component in a parent assembly context. Other examples would be a purchase order containing order line items. Each line is stritcly dependant of the order. If you delete the order you delete the order-lines, so this would be achieved with a null-relationship. The more you use Aras Innovator, the more you will find examples in the datamodel and the more you will understand why you would need to select one of the three relationship types that I mentionned when you will configure the solution for your own projects.