I have a node view and I want to display fields from one of the user profiles I setup with profile2, I have the latest version of entity api div version. I'm not using profile2 pages, because I want these to be tabs in the account overlay and I want to use them in views. If I add the User: Profile relationship, I can add the fields, but it creates a duplicate entry for each one of the user profiles (talent, brand, personal info in this specific case). So it gives me 3 results for each distinct node. Is this the right approach to the issues and do you have fixes / places to start?

Comments

sol roth’s picture

For reference and if anyone else has this issue here, You can add multiple relationships for user:profile and profile:type to the same view and then filter by profile type. This will reduce the results to 1 per user, and still give you access to all the fields in the other profile types (if you want to use them).

lucor’s picture

Thanks!

michelle’s picture

Could you explain that a bit more... I tried it and didn't have any luck and am not sure what I'm doing wrong.

I have 3 profile types and am getting 1 row per user per type. I almost wonder if this could be considered a bug...? Not sure on that so will leave the status alone. But there should be a way of getting fields from all three types into one row, I would think...

Thanks,

Michelle

clauded’s picture

Subscribing. I have the same problem and haven't found any solution to this yet : I have 2 types of profiles for my users and I want to display infos on a single line in a view.

Profile 1 : address
Profile 2 : info

I'm able to have a view that displays infos of one profile even if I specify fields of both profiles :

blank_field info1
blank_field info2

I'm also able to have a view with infos of the 2 profiles but with duplicates lines :

address1 blank_field
address2 blank_field
blank_field info1
blank_field info2

What I want is :

address1 info1
address2 info2

clauded’s picture

Finally resolved : look at this issue.

littlepixiez’s picture

Issue summary: View changes

Can we close this issue now? It looks like it may be resolved!

rajesh.vishwakarma’s picture

We can close this, #1 and #4 suggestion working fine with Version: 7.x-1.3

rickj’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.