Module builder not completing relationship setup?

[purplewave]

I've recently needed to make use of the SOAP api to interact with our Sugar installation. Everything was going very smoothly until I needed to set a relationship between a lead and a custom module developed using module builder. The relationship between Leads and my module was setup in the module builder and I know it works through Sugar as many of our employees have used it, the subpanels show up in the correct places, and the database table gets updated when associating a lead to my module.

However, no matter what I do, I always get a "Module Does Not Exist" error when trying to relate a lead to my custom module through the SOAP api. I threw some debugging code into soap/SoapSugarUsers.php inside handle_set_relationship() to find out which module supposedly doesn't exist. After checking that both the leads and my custom module are available in the $beanList array (and that I've spelled it correctly), I checked $mod->relationship_fields to see that the relationship exists. It doesn't. In fact, the relationship_fields array that is checked from within SoapSugarUsers.php is completely empty for my module despite having setup multiple relationships from Module Builder.

I added a special case to the handle_set_relationship for associating my module to a lead (much like the contacts/users relationship) and discovered this will cause the SOAP api to report success but it doesn't actually relate the two items since even when assigning the correct database field name to $key, the $mod->save_relationship_changes() call doesn't do anything as it doesn't seem to know anything about the relationship either.

I'm hesitant to override the save_relationship_changes call in my modules class to add this functionality since it's not very well commented in the SugarBean.php file and I can't afford to break the functionality of the module that currently works. Any thoughts or suggestions on how to fix this would be greatly appreciated.

Edit: I've also found that the SOAP get_relationships call doesn't return anything at all if I pass Leads and my module's name to it but returns the correct results/errors if you use Leads and a non-custom module. I saw nothing in the SOAP functions that would prevent these calls from working with a custom module so I can only assume it's something I did or a bug with module builder.

[antcrm]

Noticed the same and submitted Bug Number: 20087. ( http://www.sugarcrm.com/crm/?option=...d-47c5fb45570a )

Haven't found time yet to see whether problem lies in the Module Builder (relationships definition) or in the sugar soap code not checking relationships correctly.

[purplewave]

I've actually found the issue and just forgot to post.

Short explanation: I was trying to get the parent information based on the child id which set_relationship doesn't support.

Long explanation: The "problem" is that I setup my relationship through my custom module in the module builder, making it the parent and Accounts the child. However, I was trying to access set_relationship using Accounts as the parent. The relationship exists but due to the module names being passed in "backwards" sugar is unable to find the correct relationship or database table in which to create the relationship. One of the biggest issues in debugging this was that the error returned was "Module Does Not Exist" but it doesn't say which module (and it doesn't help that the module does exist).

I eventually broke down and added a new SOAP function that gets the relationship information by passing in the child id. I'm in the process of making this function generic instead of hardcoded values for my custom module and will try to remember to post it here when I'm done.

Edit: Corrected error message

[nickwilkens]

Any advice on how to proceed with this issue? I am running 5.0d and have the same problem.

I would be happy at this point to also hardcode the values, but am not sure where to do this.

[antcrm]

my workaround (as i recall):

-export your module created in MB (the installer, not the project), instead of deploy
-unzip the file and edit SugarModules\modules\your_module\your_module.php
-below the list of var definitions add (as example, choose modules that you need):
var $relationship_fields = Array('note_id'=>'notes', 'account_id'=>'accounts');

-save and zip again
-upload zip in module loader and install

[tomnzyoung]

The $relationship_fields array is used by SugarBean to identify the related fields to be updated when the record is saved; at 5.0 this array is hardcoded into each subclass of SugarBean - take a look at any of the standard modules and you'll see it set as part of the definitions. ModuleBuilder at 5.0 doesn't set this array for custom relationships as we only create many-to-many relationships that don't require updating related fields.

At 5.1 though we now can create one-to-many and many-to-many relationships and so we bumped into this problem when updating ModuleBuilder for the new relationship types. The solution we used was to add a 'save' property to the relate field definitions to be used in SugarBean->save_relationship_changes(), and over time we think we'll move away from the hardcoded approach to this new relate field property for standard modules.

Cheers,
Tom

[cainmi]

@tomnzyoung,
I'm not quite sure if I understand your answer - is this issue solved in 5.1? Doesn't seem like it. Any tips?

@purplewave,
Just wondering if you got around to generalizing that function you made?

Thanks guys.