model.save() over write the full bean instead of just set fields

Question

Hello Folks,

I have find out a big problem with sugarcrm.

I have created the custom popup for Accounts module by following Adding a new popup view in Sugar 7.x Record View « Sugar Developer Blog – SugarCRM and it is working fine.

Now Suppose I have Industry field on the model popup. So I have used the code

this.model.set('industry'.'value');
this.model.save();

and industry field is updated with the value that I have been set on the model.
BUT

if you open the model and then open the same record into next tab and change the Name field on the record to suppose 'XYZ' . Now go back to previous tab and apply the changes on the model to set the Industry field.

This should and suppose to just update Industry field but it update the name field with the previous one. It revert the name field as well.

This means this.model.save(); not just update the fields which we set using this.model.set(); it updates all the fields. full bean.

I have tried to save like below

this.model.save({industry:'value'});

but it is having the same effect. it update the full bean.

As of Backbone.js v0.9.9, you can simply pass { patch: true } to save().

I have tried the same but it seems like sugar has not implemented patch.

create → POST /collection
read → GET /collection[/id]
update → PUT /collection/id
patch → PATCH /collection/id
delete → DELETE /collection/id

One record is updated by many users from different departments. And if any changes apply from the model popup and mean while the record has updated by some one then it over rite all the changes of the other users.Can some one give some thoughts on this how to over come from this situation and what is sugarcrm guys answer on this?Patrick McQueen Matt Marum Francesca Shiekh Alan Beam Hiren Darji

Prashant Patel · Accepted Answer

Hello Matt Marum , Thank you so much for spending time to answer my question. 1) We are using model popup ( customized ) to populate data and then apply that changes to model again. So we can not show conflict again on the apply changes from model. 2) Even sugarcrm conflict gives you 2 options like, keep your changes or keep other changes. But we have situation that requires to merge both changes. As per your words : I think the best practice is to try and avoid situations where multiple users are trying to modify same record at same time. SugarCRM is big platform and design to use for many users and they should allow to edit the same record . If this is one of the sugarcrm limitation then I was not aware of this. Because we have so many users as well as the portal users , so of course there will be a chance that same record will update by many users at the same time. I think you ( SugarCRM Engineer Team) or we ( SugarCRM Developer ) has to find the solution for this kind of situation. I am not getting why SugarCRM is not using or thinking to use PATCH method which is supported by backbone as well ? Also why sugarcrm does not show the merge request as a third options on conflict ? 1) Apply your chages 2) Apply other user changes 3) Merge your changes with other user changes. I have got the work around that I need to retrieve the bean again into model just before going to save the bean. But this is not the fair enough solution as I have to retrieve bean 2 times...first time to fetch the information and show on model. Second time before model.save(); Can you please give some good solution to over come from this kind of situation ? As this is very normal usage of sugarcrm as a large extensible system for large no of license users company. Thanks Prashant