Relationships Confusion

[tomcdonnell]

I am confused by relationships between modules in general.

From studio->campaigns->relationships, the campaigns module can only be linked to other modules using a one-to-one relationship. Yet from studio->documents->relationships, the documents module can be linked to the campaigns module using a one-to-one or one-to-many (but not a many-to-many) relationship.

Questions:
* Why are some relationships between some modules unable to be created using studio?
* Why can some pairs of modules be linked one-to-many in one direction, but not many-to-one in the other direction?

[agcopley]

I am confused by relationships between modules in general.

From studio->campaigns->relationships, the campaigns module can only be linked to other modules using a one-to-one relationship. Yet from studio->documents->relationships, the documents module can be linked to the campaigns module using a one-to-one or one-to-many (but not a many-to-many) relationship.

Questions:
* Why are some relationships between some modules unable to be created using studio?
* Why can some pairs of modules be linked one-to-many in one direction, but not many-to-one in the other direction?

There is a bug in the campaigns module that prevents 1:M relationships being made. Rather than fix it Sugar just prevent you from making them. Good eh?

[datasponge]

Also, in addition to Campaigns relationship being hard-coded as One to One, Studio and Module Builder don't allow you to create a Many to One relationship.

I don't know the reason and it never made sense to me since, particularly in Module Builder I see the most common scenario being a new module with a Many to One relationship to Accounts or Contacts.

The workaround is to create the module in Module Builder, then go to Studio and create the relationship from the module on the One to Many side. Kind of a pain that you can't complete the design in Module Builder if you ask me.

Phil