[<@U07MA07KQKS> - Old Problem <https://community.g...
# gd-beginners
Hi, I came from this thread (link) but I couldn't access it. I had a similar problem, but I solved it by creating a bridge table saying the role and having the M:N. In my case, it's a soccer match with a home and away team and I couldn't have the double link. So the bridge table ended up with the foreign key of the team and the match and an attribute called "role". I don't know if this is the best way, but it seems to me that at the modeling level it solved it. Did you manage to solve it that way? Best regards
m
Hi Felipe, yes your approach to resolving this issue was the same as in this thread: https://community.gooddata.com/t/23124579/hi-there-i-m-new-to-gooddata-and-i-m-working-on-building-my- Our team recommended to I recommend to leverage the M:N relationship in their LDM: https://www.gooddata.com/docs/cloud/model-data/evolve-your-model/many-to-many-in-ldm/#Many-to-ManyinLogicalDataModels-SetupMNrelationshipsinLDM As in your case, this allowed them to create connections between the dataset objects as desired.
f
Hi @Michael Ullock, how are you? Thanks for your message In the end, M:N needs a reference in both tables and it didn't work out very well. The modeling ended up like this But I still insisted on the bridge table. There is still a warning that I intend to remove, but I need to think about the modeling.... Best regards,
👍 1