Thread

Hi guys,

I already stumbled into Playa for 2.x, but basically all I need is to do what Multi Relation does (which unfortunately is only 1.x). Any thoughts on this? Is there an alternative to achieve what I’m trying to do (i’m trying to relate multiple services to single cases, which are both channels, in my portfolio)?

Thanks 😊

Playa is it unless you need only one to many (or reverse), in which case you can use the built-in relationships.

Well I already managed to get a dropdown showing the related channel, but I want to be able to select multiple entries from the related channel… That’s a many to one right?

Many to one would essentially be reverse relationships.

Ok, so I found P&T Field Pack on GitHub, and was wondering whether it would work to fill it using the Query module? Or is the parsing order wrong for that?

You’ve lost me, I’m sorry.  Can you explain what you are trying?

Sure, sorry if I wasn’t clear enough. I have two channels:

- Cases
- Services (front-end, cms-implementation, e-mailmarketing, social media)

When I add an entry to the channel “Cases”, I want to be able to select which services i delivered. I’ve found “P&T Field Pack” on GitHub (http://github.com/brandonkelly/pt_field_pack, P&T created Playa I think aswell), which has a “Multi-select” field. This sort of does what I want it to, except for the fact that it’s static (you have to preset options which you can select while publishing). So I thought: what if I declare a query where you’d normally set the options, sort of like this (warning: aircode ahead)

{exp:query sql="SELECT title,id FROM entries WHERE channel == services"}
{title} : {id}
{/exp:query}

If it would be rendered properly during publishing, this would return the id’s of the cases I’ve selected, then all I’d have to do is loop through those entries with exp:channel:entries by passing the id’s on to that… Am I making any sort of sense?

There is also a first-party multi-select field, as well as checkboxes and radio buttons, etc.

I would probably just use categories for your services rendered, though.  I think you may be over-complicating things, we see this somewhat commonly with experienced developers - but experienced in other systems. =)