[SalesForce] Error: Compile Error: Comparison arguments must be compatible types: Schema.SObjectField, String at line 8 column 113

trigger quantity on OpportunityLineItem (after update){
    set<id> lineset= new set<id>();
    for(OpportunityLineItem ql: trigger.new){
      if((trigger.OldMap.get(ql.id).Quantity!= ql.Quantity)){
           lineset.add(ql.opportunityId);
      }
    }
    list<spr__c> sprlist=[select Status__c,spropportunity__c from spr__c  Where spropportunity__c in:lineset && spr__c.Status__c=='approved||draft'];
   if(sprlist != null && sprlist.size()>0){
           for(spr__c s : sprlist){
               s.Status__c = 'obsolute';
           }
           update sprlist;

       } 

    }

Best Answer

Some operators you are using are different in SOQL. Change the query to:

list<spr__c> sprlist = [
        select Status__c, spropportunity__c
        from spr__c
        where spropportunity__c in :lineset
        and Status__c in ('approved', 'draft')
        ];

Related Solutions

[SalesForce] Compile Error: Comparison arguments must be compatible types

The line provoking the error is actually

System.assert(e.getDmlFields(0)[0] == 'Email');

The error is complaining that you're comparing a Schema.SObjectField value with a String, which isn't allowed. It looks like getDmlFields() has changed over the releases. I'll raise a doc bug to get that example code fixed. Changing that line to

System.assert(e.getDmlFields(0)[0].getDescribe().getName() == 'Email');

should fix the error.

System.assert(condition) is used in test code to check that a given condition is true. If the condition is false, the test as a whole fails, and the location of the failure is given in the test output log.

Working through the asserts in that example:

System.assert(false); says that you should never get to that line - the insert is expected to throw an exception.
System.assert(e.getNumDml() == 1); says that the failure concerns a single record
System.assert(e.getDmlIndex(0) == 0); says that the failure was on the very first inserted record
System.assert(e.getDmlFields(0).size() == 1); says that the failure was caused by a single field in the offending record
System.assert(e.getDmlFields(0)[0].getDescribe().getName() == 'Email'); says that offending field is called 'Email'
System.assert(e.getDmlMessage(0).indexOf( 'A lead with this email address already exists.') > -1); says that the error message should match the expected value.

Basically, the test method is checking that the trigger executed EXACTLY as intended!

The exception methods, such as getNumDml(), are listed here.

[SalesForce] How would one track field history for OpportunityLineItemSchedules

I played around with this and found that if I edited a single OpportunityLineItemSchedule record, all of the records associated with that line item were deleted and a whole new set of records were inserted. I thought that maybe the old records would at least be kept around with IsDeleted=TRUE but that was not the case.

Based on this evidence, it appears to me that you will need to have both delete and insert trigger logic on the OpportunityLineItemSchedule object and correlate the events using the OPPORTUNITYLINEITEMID field.

This Salesforce implementation of delete/insert records probably makes sense since you can imagine it is easiest to simply recalculate the whole schedule anytime a value is modified (e.g. number of payments or period type).

Best Answer

Related Solutions

[SalesForce] Compile Error: Comparison arguments must be compatible types

[SalesForce] How would one track field history for OpportunityLineItemSchedules

Related Topic