[Resolved] Big problem for small problem

[Author]

Posts

[Minesh]

With your case the issue is not is not M2M but O2M but how you want to group your results as you asked here:
=> https://toolset.com/forums/topic/big-problem-for-small-problem/#post-632153

and as I tried to explain here - there is no direct way to group results by parent having filters added to child view:
=> https://toolset.com/forums/topic/big-problem-for-small-problem/#post-632733

You can obviously create One-One OR One-Many OR Many-Many post type relationship and it should word as we stated with our Docs.

[Franck]

No, you don't understand my last question.

Let forget the group by...

I have to know the consequences when you use M2M although my relation is One to Many.

Because if i use the M2M i could filter by the commun field.

[Minesh]

Because if i use the M2M i could filter by the commun field.
==> Yes - you will be allowed to filter by common field when you setup relationship as Many-to-Many but unfortunately I do not have any information yet to share how that filter will work OR how you can add it as you know and already communicated with you that it's yet to be implemented. I can tell you something about that when we implement it and we have official Docs published that explains how to use that filter.

[Franck]

I know that you answer, it is not my question.

I have to know the consequences when you use M2M although my POST relation is One to Many.

[Minesh]

If your relationship is One to Many - you should implement One to Many relationship. I do not follow you what you want to do with Many to Many relationship as you already know that you need to setup the One to Many relationship with your CPT. I'm not following you when you say "I have to know the consequences when you use M2M although my POST relation is One to Many." - even I do not know the reason.

For now - you can only add custom fields to the intermediate post type when you build Many to Many relationship. You can not add custom fields when you build One to one OR One to Many relationship. You can display it only related posts using views.

So - If you establish many to many relationship between your post types, when you connect the posts it will create additional post every time for intermediary post.

[Franck]

Hello,
I ask that because it was your advice to use the new relationship even i said you i used a One to Many relationship.

It would be help me because in this case i would not need to fill my commun fields in parent and child CPT.
I remember you my first problem, i cannot filter by parent and child in the same time so i have to duplicate the parent fields int the child fields.

Do you follow me ?

Thanks a lot

[Minesh]

Yes - I follow you.

I ask that because it was your advice to use the new relationship even i said you i used a One to Many relationship.
==> The advise is because you wanted to filter with intermediary post type filed that is why it was advise and you need to make decision which post relationship type you need to use. So - you should better play with Betas and try to build both relationship as a test example and check which relationship best suits your requirement.