Feed

Please see this example code and the video on how I put this all together with a minimum of writing code on my own: 

q = load "opportunity1";
start = filter q by date('CloseDate_Year', 'CloseDate_Month', 'CloseDate_Day') in ["1 week ago".."1 week ago"];
start = group start by all;
start = foreach start generate sum('Amount') as 'A', "1-start" as 'Bucket';
q_A = filter q by date('CloseDate_Year', 'CloseDate_Month', 'CloseDate_Day') in ["1 week ago".."1 week ago"];
q_B = filter q by date('CloseDate_Year', 'CloseDate_Month', 'CloseDate_Day') in ["current week".."current week"];
diff = cogroup q_A by all full, q_B by all;
diff = foreach diff generate sum(q_A.'Amount') as 'A', sum(q_B.'Amount') as 'B';
diff = foreach diff generate B-A as 'A', "2-difference" as 'Bucket';
result = union start, diff;
result = group result by 'Bucket';
result = foreach result generate 'Bucket', sum('A') as 'value';

Hi, 

For this requirement use aggregate result to easily and effectively manage the sum of quantities for triggering opportunity line items record. 

Create a new account instance , populate id and the quantity field then add the account instance to an account;s list and update that list. 

You can fetch the account id and related quantity using following snippet

//OppIds is the set of opportunity Ids of triggering opportunity line item records
for (AggregateResult arr : [select Sum(Quantity), OpportunityId,Opportunity.AccountId from OpportunityLineItem where OpportunityId in :OppIds Group By Opportunity.AccountId,OpportunityId]) {            
         Account Acc= new Account();
         Acc.id =String.valueof(arr.get('AccountId'));
         Acc.custom_field_for_quantity__c =String.valueOf(arr.get('expr0'));
    }

Hi Filip,  

I think that you can have the stationary asset (or any other emission source) registered, and the way of "ignoring" it is with the "0" energy use record. So if the store is in "building" stage, you can register as new StatAsset, and will not have Energy Use. In that way, you have it in the inventory and will not produce carbonfootprint.

Try searching without the commas and see if they show up. This might be one of those characters that get stripped before loading into the database. This happens for quotes as well.

Hello,

Are you sure the record meets the initial criteria of the approval?

Hi, 

This error occurs when your Apex code exceeds the governor limit of 100 synchronous SOQL queries in a single transaction. 

To fix the error "Too many SOQL queries: 101" : 

1.

2. Implement Batch Apex and Future Methods

3. Avoid DML operations inside loops

Thanks