Custom Bean File Parent::save help please!

[mipapage]

Hi there,

We have some custom modules. Module A is one-to-many Module Z, such that there is a listview of Module Z present in Module A.

Now, we have some Custom Bean work being done in the {module}.php file of Module A, extending the module_sugar class. In that we have:

function save($check_notify = FALSE) {
// Some logic here
parent::save;
}

This custom logic works well. However, when we try and add an entry of Module Z to Module A, the data for Module Z is saved, but the relationship between the two is not stored.

If we remove the custom Save, the relationship saves properly. So, do we have to manually update/save the relationship in this case, or is there a function that I can fire that will handle this for us?

[rafael.q.g@hotmail.com]

I workaround for this problem is instead of customize save function use a logic_hook on before_save event.
Then you can process your logic and use the standard save function.

[lijith]

To setup a relatioship dynamcally refer the link SugarCRM: Set relationship dynamically « Php Bugs

[mipapage]

Thank you both for the answers.

1. I'm not a fan of using those hooks as it becomes more complicated setting up the manifest files and the like for subsequent deploys and avoiding overwriting of the custom code...
2. As for the relationship, that is already built via Studio.

It seems that by custom coding save we're overwriting something in the Sugar Bean that normally handles this, so we are just going to code these bits in by hand to our save method.