Hi All,
I have scenario if record is created by specific user and record already exists by specific field_name in system the don't save it just log in SugarCRM log or in my custom failure log module add log entry and I want to check this condition in before save hook.
Can anyone suggest please?
Kindest Regards,
Shreya
Hi Shreya,
The best path IMO would be to stop script execution on the server with an API exception. Preventing a save from happening in any other way usually leads to bigger problems in one way or another from my experience.
throw new \SugarApiExceptionError('Duplicate record found!');
I would do my best to avoid this scenario by adding some kind of UI validation to prevent the save process from even starting if a duplicate is found. You can accomplish this with field validation by making a request to the server to check if the record already exists when a user clicks the save button:
https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_13.0/Cookbook/Adding_Field_Validation_to_the_Record_View/index.html
My company also offers a plugin call Deduplicate which allows an administrator to define rules and prevent record creation if duplicates are found if that is something you might be interested in:
https://upsertconsulting.com/plugins/deduplicate/
Hope this helps!
Hi Francesca Shiekh,
Stopping a save in the view controller or rest endpoint is fine - you would just want to make use API exceptions for anything being called from the Sidecar UI so that the app can handle any errors appropriately. The "bigger problems" I'm referring to are just that I've seen developers try to delete the bean or fetch an existing bean over the new bean being created during the before_save hook process and it can cause UI and data issues, especially with relationships.
