Relate custom module to subpanel for 5.2.0c

[Gebremedhin]

Hello all,

I have created a custom module in module builder, built relationships in it and added subpanels for them. I am finding that although the subpanel shows up the relationship isn't complete. For example, I have created a module called events (different from the built-in version) and a module called venues and related venues to events by using related fields and adding a many-to-many relationship between the two modules and then deploying. I find that when I create an event and then add the venue from the create window it shows in the events modules but not in the subpanel for the venue in the detailview. But if I create the event from the subpanel in the detailview for that venue it will show in that subpanel. I understand I need to do some extra work with the files but all the instructions in the forum seems to be for various versions and I think some of that has already been built into version 5.2.0c but I don't know how much. Can someone give me the steps I need to perform to be able to get custom module data to show up in a subpanel's custom module regardless of where the record was created?

Thanks,
Hassab

[Gebremedhin]

Nevermind, think I found the instructions:

http://developers.sugarcrm.com/docs/...05.2.1.40.html

[Gebremedhin]

OK, question still open. I followed the instructions and the relationship is complete. However, tagging a record via a related field built into the module does not seem to be creating an entry in the relationship table. Anyone know how to make that happen?

Any help for a newbie would be much appreciated!

thanks,
Hassab

[Gebremedhin]

I have resolved this:

1 - my faulty logic, you'd need a multi-select field to make a relate field work in a many-to-many relationship. For now I can use the subpanel buttons that do appear when I create the many-to-many. I may later want something fancier but too new right now.

2 - I did find when creating a one-to-many using 2 custom modules the relate field didn't automatically appear. I had to create it myself and make sure the system label matched the label specified in the vardefs file for that module. That seemed to make everything work fine.

-Hassab