How to prevent logic hook firing from another module or on import

Hello Daniel,

I believe you are new to SugarCRM. There are a few improvements I would suggest that you make to your code.

For example, I suggest that you use SugarQuery instead of using raw SQL query for your select statement.

https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_9.2/Data_Framework/Database/SugarQuery/

Secondly, regarding your question,

There must be a bean of opportunities getting saved in one of the accounts logic hooks. You can set the

$bean->processed bit to true if you don't want the logic hooks to trigger after the bean is getting saved.

Or you can set a custom bean property like

$bean->came_from_account = true;

and then in your logic hook in opportunities, you can check where the bean save came from.

Inside the logic hook write:

if ( $bean-> came_from_account != true){

//logic hook code

}

Kind Regards!
Rolustech Support
Email: support@rolustech.com 
Website: www.rolustech.com 

Hi Hussain.

Thank you for your reply, what is the benefit of SugarQuery over pure SQL? They both have the end goal of assigning data to variables but I find sugarQuery much harder to read (I am of SQL background).

Thank you for your help and I'll try to implement this instead!

Thanks,

Daniel

Hi Hussain.

Thank you for your reply, what is the benefit of SugarQuery over pure SQL? They both have the end goal of assigning data to variables but I find sugarQuery much harder to read (I am of SQL background).

Thank you for your help and I'll try to implement this instead!

Thanks,

Daniel

Hi Daniel,

Two reasons to consider SugarQuery:

• Even if you are of SQL background (as many of us are), it does not mean we don't still make mistakes every now and then - eg forgetting an apostrophe in the wrong place. By wrapping an object layer around that, we reduce the opportunity for accidents ending up in production.
• It makes your queries more portable between different database servers - may not be relevant for the implementation you're working on today - but I know a lot of people build libraries of code they reuse in different parts of an organisation, and you may one day reuse that code in a next client - or wish to share it publicly. SugarQuery makes that a lot easier.

Equally, I acknowledge that it takes a bit more time to learn, and you may not feel its justified if you're just working on the one query that will never get used anywhere else. 

Regards,

Adam

Daniel Hill,

Definitely i would use SugarQuery, also for security reasons (eg: what if a malicious user (or an integration coming from malicious places) pushes into your crm a record with id something like '"; truncate opportunities; --' ? The good old bobby tables!

Even if it won't work due to further sanitisation, you get my point. Prepared statements would add an additional layer of protection thanks to SugarQuery.

There is also an alternative ORM way of achieving what you attempted to do: "does this opportunity have any contacts related to it?" see here: https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_10.0/Data_Framework/Models/SugarBean/#Fetching_Related_Record_IDs

Finally, that type of validation I would probably put it on the api itself. I would extend the PUT /Opportunities/<id> api with this additional check. That way it would not trigger on imports, but only when an edit fires from the api perspective (if that's your overall objective).

Cheers