Columns from parent entities sometimes not available in views

[Gilles12]

Hello.

I am struggling to have columns from some parent tables available to add to views.

For some tables, parent tables are present in the Related tab when adding columns, but for some other tables, the Related tab contains only tables from standard relationships (Created By, Modified By, Owned By...). So in this case only the primary column of the parent tables is available to add in the view.
Between the two situations (parent tables present or not present), I have not found any difference in the way parent and child tables are setup in their relationship for example. I see that I am not alone to face this issue, but no suggested solution that I have read applies. All customizations are pusblished, all tables are included in the solution, the searchable attributes are set both sides, etc. I don't know what other direction to explore...
Thank you for your ideas...

[Jmanriquerios]

Hi @Gilles12 

This issue has to do with the structure of the relational model that you have set up.

For example you have a table A and a table B with a relationship from table A to Table b 1:N

If in table B you would like to see the fields from table A in the related fields, you can do so. On the other hand, in table A you could not show the fields of table B in the related ones

[Gilles12]

Hi @Jmanriquerios.

Thank you for your answer. However following your example, it is really in table B that I don't have table A columns included (except the primary column). I have a lot of 1:N relationships in my model. Just one example, I have a Deal to Booking (1:N) and I perfectly see the Deal table in Related and all its columns. Many others are working well. I have exactly the same relation (1:N) from Survey Question to Survey Response and in the Survey Response I can't see Survey Question table and columns (except again the primary column). This 1:N relation works perfectly for other purposes, like to have a subgrid, but in the view used in this subgrid, I can have only the primary column of the Question. So there is something, but I can't find what!
Please see my illustration attached.

[Jmanriquerios]

Hi @Gilles12 

The image is not shown, can you send it again?

[Gilles12]

Perhaps better in the message itself...

[Jmanriquerios]

Hi @Gilles12 

There seems to be something wrong with the relationships, because in principle it should be a single relationship, it's just that seeing it from one side or the other is what changes but it is a single relationship.

My example, the products table is the parent and the offer product table is the child

When I see it in the offer it appears as a 1:N relationship

When I see it from the offer product it appears as an N:1 relationship

Everything seems to be the same, something is wrong in your environment,

[Gilles12]

I understand your point, however I just deleted the relationship visible on the Survey Question side (after removeing the Question column from the view because it was a dependency), and it has deleted automatically the other (so for me it is the same visible both sides). Then I recreated the lookup column in Survey Response, and the relationship is now visible both sides again, exactly as the first time. I just did the same as the first time, which is basically to create the lookup column. Not more!

You're right in the sense that with my old Deal to Booking relationship, it is visible only on the Booking side (and probably the same for all my other relationships in the model).

So there is something with my new tables that makes the relation visible both sides and prevent to use it normally!! Very very strange!

[Gilles12]

Some good news but still weird in the relationship side!

After I recreated the relationship after deletion (as I said just by recreating the lookup column), now all is working fine. But trust me, the new relationship is still visible both sides, exactly the same way than before! So there was "something" the first time, I will never know what.

Also, I had the same issue with a second parent table. I did the same deletion and recreation of the lookup column, and same result. It works but the relatiosnhip is also visible both sides.

See that now I can get both parent tables and all their columns in the view:

Relationships in Survey Responses (normal):

Relationship still visible in parent Survey Question:

Relationship still visible in parent Survey Response Set:

What do you think?

[Jmanriquerios]

Hi @Gilles12 

I don't know what you are doing, but it is really a single relationship that is created, for example if you create it from table A to table B, you must create it as a 1:N relationship, or if you create it from table B to A, you must create a Lookup field.

Check because I think you are creating relationships twice.

[Gilles12]

No really I have just and only created the relationship on the N side, while only creating the lookup column. It was what I have done the first time, and then what I have done the second time also after deleting the relationship. When I deleted the relationship, it disappeared on both sides, and when I recreated the lookup column, the relatioship was again visible both sides.
I understand all what you say. I believe you, what you say is purely logical. On my side, I can just say what I have  done and what I see. As it is working perfectly in the view, it seems this "strange" relationship is not the reason why it was not working.
Anyway, all is working fine now. I appreciate your help and I will pay attention to future behavior. As I created a ticket to the support team and I cancelled it, they asked me more for more info anyway, so let's see if they have an explanation.
Best regards,

Gilles.