Hi Whyser,

 I have written new trigger for that to achieve. But I will not be able to achieve expected result. Please look into the code. If I missed anything please let me know.

trigger UpdateSalesOrderfromAccount on Account (after insert) {
  
  for (Account acc : Trigger.New) {
    WebServiceCall.callservice(acc.Id, acc.Name);
  }

//before update
      List<Id> idsToQuery = new List<Id>{};
      for(Account acc : Trigger.new) {
         idsToQuery.add(acc.id);
      }
//Now query all related Sales Order
      Sales_Order__c[] sales = [select id, Name, DESCRIPTION__c from Sales_Order__c where id IN :idsToQuery];

//Loop through Sales Order
      for(Sales_Order__c s: sales){
    
    //Using the trigger.newMap, get the related Sales Oredr record to the specific Account record
      Account a = Trigger.newMap.get(s.Id);
   
    //Set the Last_Case__c field here....
      s.DESCRIPTION__c = a.For_Testing__c;
}


//Update all records in a single statement
update sales;
   
}

Also suggest me how I can convert this trigger to Apex method. Because I am planning to call this method when inserting Web service records to an object. If I write the Apex method, I don't know how I can  pass in the newly created Account object's ID to Sales Order query as I can pass the new Id in trigger when trigger takes place.

Please do the needful. This is the very important requirement for me. I hope you can resolve my problem.

Waiting for your kind suggestion.

Thanks a lot in advance.

:smileymad::smileysad: 

HI,

      Yes, you are right. I am putting my webservice call in scheduler and then I will have to run only second part part of the above code. But I am getting the error.... i.e for the below line:

// You need to pass in the AccountID into the get call rather than the Sales_Order__c's ID
      Account a = Trigger.newMap.get(s.Account__c);

I am getting this  Error: Compile Error: Invalid field Account__c for SObject Sales_Order__c at line

 But as per your suggestion, How I can put the AccoutId into get call rather than Sales_Order__c's Id? Here Account is default object. I will not be able to run the code even if I mention s.Account or s.Account__r.Name or s.Account.Name also. If I put the s.Name related to Account in that place, code is working fine. But I am not getting any expected result.

Could I know whether this code(above) will be able to create the Child object related to Parent when I upsert the web service data to parent object.

I also tried below method to update the child record related to parent. But still I am unable to get the expected result. My expected results are:

1) Code has to create a new Sales Order (child) record.

2) This newly created child record has to associate/update in parent record.

3) When I click on the single Account(parent) record in the Account list view, detail view should contain the child records which are related to parent and should display under seperate block(When I click the Id/Name of this child record, the link shoud navigate to perticular child record view page).

trigger UpdateSalesOrderfromAccount on Account (before update) {
  
  // The map allows us to keep track of the accounts that have
    // new addresses

    Map<Id, Account> acctsUpdate = new Map<Id, Account>();

    // Trigger.new is a list of the Accounts that will be updated
    // This loop iterates over the list, and adds any that have new
    // addresses to the acctsUpdate map.

    for (Integer i = 0; i < Trigger.new.size(); i++) {
        if (Trigger.old[i].Description != Trigger.new[i].Description) {
            acctsUpdate.put(Trigger.old[i].id, Trigger.new[i]);
        }
    }

    List<Sales_Order__c> updatedSales = new List<Sales_Order__c>();

    //Here we can see two syntatic features of Apex:
    // 1) iterating over an embedded SOQL query
    // 2) binding an array directly to a SOQL query with 'in'

    for (Sales_Order__c s : [SELECT id, DESCRIPTION__c FROM Sales_Order__c WHERE id IN :acctsUpdate.keySet()]) {

        Account parentAccount = acctsUpdate.get(s.id);
        s.DESCRIPTION__c = parentAccount.Description;
        
        // Rather than insert the Sales_Order__c individually, add the
        // Sales_Order__c to a list and bulk insert it. This makes the
        // trigger run faster and allows us to avoid hitting the
        // governor limit on DML statements

        updatedSales.add(s);
    }       

    update updatedSales;

  }

Please let me know your suggestions.

Thanks for your all comments.

:smileymad: :smileymad: :smileysad::smileysad: