Firstly I will describe how my content types and views looks like.

Two content types:
Server
Project

Relation between them:
Server Projects(many to many)

View:
Project View (place where Im showing informations about current project and list of related servers)

View relationships:
Relation: node -> endpoints[Server projects])
(Endpoints::Server projects) Relation: endpoints[Server projects] -> node)

I'm getting correct list of related servers BUT I can't add field "Rid", why? I need this field for my "Delete relation" link. I can add only one field from "Relation" group and this is "Relation: endpoints".

My Relation module release date is 11 december.

Before update I was using "Rid" field without any problems.

Comments

solotandem’s picture

solotandem commented
Category: bug » support

Refer to the list of relationships in http://drupal.org/node/1361780#comment-5345274 and http://drupal.org/node/1361780#comment-5361260. What is the base table for the view? If relation, then you should be able to add rid field.

Can you apply the patch from http://drupal.org/node/1361780#comment-5361260? These new relationships allow you to have either content type as the base table to the view, if that is helpful.

MeDAN’s picture

MeDAN commented

My base table is a node not relation so thats why im not able to add RID field. I want to have simple relation node<->node + relation info.

Why node<->node can't get relation table with all relation extra fields ?

While using node<->node->relation we can't get correct results because (n<->n)->relation incorrectly verifies directional when my n<->n is a directional relation.

solotandem’s picture

solotandem commented

If you redo the view with relation as the base table and add relationships using the pattern in 1361780#comment-5345274, then you should be able to display rid and any fields attached to (or a part of) the relation.

Is this suggestion doable for you?

solotandem’s picture

solotandem commented

In the patch attached to 1361780#comment-5381108, I added a relationship from endpoints to relation. This relationship will allow you to keep node as the base table for the view and display fields from relation table (and any fields attached to the relation).

Try it out.

mustanggb’s picture

mustanggb commented
Component: Code » API
Status: Active » Closed (fixed)

Views integration in latest dev has changed significantly
Suggest this issue no longer exists or at the very least needs to be checked again

mustanggb’s picture

mustanggb commented
Component: API » Views

So apparently "Component: Code" doesn't exist anymore