Modify return data from related field

If I understand correctly you have an Account on an Opportunity.

When you select an Account on the Opportunity you want to copy field my_account_field from Accounts to field my_opportunity_field on Opportunity but the user should be able to change the Opportunity field from that default if they wish to do so.

I am assuming Account is a Relate Field on Opportunity so the Opportunity will have an account_id

I would do this as an on.change on the account_id field on the opportunity in the Opportunity's record and create-actions view and check that the opportunity field is not already filled (you don't want to override what it was set to on an existing opportunity when it's edited).

You will need something like:

In custom/modules/Opportunities/clients/base/view/create-actions/create-actions.js

and similar in  custom/modules/Opportunities/clients/base/view/record/record.js

({

  extendsFrom: 'CreateActionsView',

  initialize: function(options){

    this._super('initialize', [options]);

    this.model.on('change:account_id', this.populateMyOppField, this);

  },

populateMyOppField: function(){

   //if the account field on the opportunity is not empty (we just changed it and it could have been deleted)

if(!_.isEmpty(this.model.get('account_id')) {

     //if the field on the opp is not already set, you'll need this more on edit than create not to override prior values

      if(_.isEmpty(this.model.get('my_opportunity_field'))){

         //get the account bean

         var accountBean = app.data.createBean('Accounts', {id: account_id});

         requestAccount = accountBean.fetch();

         requestAccount.xhr.done(function(){

           //once you have the Account information you can copy my_account_field to my_opportunity_field

           this.model.set('my_opportunity_field', accountBean.get('my_account_field'));

         }

     }

   }

},

});

Note the code is just intended to give you an idea, it is not tested, it's written off the cuff, so there could be syntax errors.

There may be a better/easier way of doing this.

HTH

FrancescaS

Thanks a lot!! Worked perfectly . But i have a question, why extends the CreateActionsView? this manages the events in the record view?

Hello ,

Francesca , do you know if this would be possible to do in reverse ? I guess calling model.set on the account.bean is not possible ? So would have the update it with an app.api.call ? app.api.call('update', app.api.buildURL('Accounts/'+accountid), {"accountfield" : "value" }, callbacks...  ?

So you want to update the related Account from within the Opportunities view controller?

You should be able to do that:

         //get the account bean

         var accountBean = app.data.createBean('Accounts', {id: account_id});

         requestAccount = accountBean.fetch();

         requestAccount.xhr.done(function(){

           //once you have the Account you can update the values you need to update

           accountBean.set('the_field', the_value);

            // save your changes

            accountBean.save();

         }

HTH

FrancescaS

Oh Interesting thanks! So many ways to skin a cat.

Did it with the api.call initially

The bean.set offers superior performance I would reckon since there is no network overhead ?

requestAccount.xhr.done(function(){
  //once you have the Account information compare the visit dates
  if ( moment(pcaDatVisite).isAfter(accountBean.get('v_der_date_visite_c').substr(0,10))) {
  //update the date visite of account using api.call
  //once you have the Account you can update the values you need to update


  accountBean.set('ca_autocompl_c', new Date(pcaDatVisite));
  // save your changes
  accountBean.save();
  /*
  app.api.call('update', app.api.buildURL('Accounts/'+relAccId), { "v_der_date_visite_c" : new Date(pcaDatVisite)}, {
  success: _.bind(function(response) {
  //response comes back from your api, maybe you want to set some value on your model or alter a response?
  }, this)
  });
  */
  }
  });

Oh Interesting thanks! So many ways to skin a cat.

Did it with the api.call initially

The bean.set offers superior performance I would reckon since there is no network overhead ?

requestAccount.xhr.done(function(){
  //once you have the Account information compare the visit dates
  if ( moment(pcaDatVisite).isAfter(accountBean.get('v_der_date_visite_c').substr(0,10))) {
  //update the date visite of account using api.call
  //once you have the Account you can update the values you need to update


  accountBean.set('ca_autocompl_c', new Date(pcaDatVisite));
  // save your changes
  accountBean.save();
  /*
  app.api.call('update', app.api.buildURL('Accounts/'+relAccId), { "v_der_date_visite_c" : new Date(pcaDatVisite)}, {
  success: _.bind(function(response) {
  //response comes back from your api, maybe you want to set some value on your model or alter a response?
  }, this)
  });
  */
  }
  });

I would think the bean.set leverages the api, so the performance wouldn't necessarily be better one way or another. After all both need to affect the database.

FrancescaS