标签 salesforce 下的文章

Salesforce SOQL中的Semi-Join和Anti-Join

半连接和反链接是SOQL里面一个宝,只要用的好,天天下班早

Semi-Join | 半连接

半连接(Semi-Join)指的是在SOQL语句的对比子句里面(也就是WHERE部分),使用子查询(subquery)的情况。

可能用到半连接的情况可能有:

  1. 获取某些具有特定阶段或者截至日期Opportunity的Account下面所有Contact信息
  2. 获取具有激活的Contract的Account下面所有的Opportunity信息

写法
有两种半连接:1)使用Id字段,2)使用外键(Lookup/Master-Detail关系等)

  1. 使用Id字段的半连接例子:
SELECT Id, Name 
FROM Account 
WHERE Id IN 
  ( SELECT AccountId
    FROM Opportunity
    WHERE StageName = 'Closed Lost' 
  )
  1. 使用外键的半连接例子:
SELECT Id
FROM Task 
WHERE WhoId IN 
  (
    SELECT Id
    FROM Contact
    WHERE MailingCity = 'Twin Falls'
  )

Anti-Join | 反连接

反连接(Anti-Join)与半连接非常类似,只是不同于半连接使用的比较关键字为IN, 反连接使用的比较关键字为NOT IN。其余部分包括写法、限制等是一致的,不再赘述。

两种写法

  1. 使用Id字段的半连接例子:
ELECT Id, (Select Id, Amount, CloseDate FROM Opportunities)
FROM Account
WHERE Id NOT IN
  (
    SELECT AccountId
    FROM Contact
    WHERE LastName LIKE 'Trump%'
  )
  1. 使用外键的半连接例子:
SELECT Id, Name, Phone, Email
FROM Contact
WHERE AccountId NOT IN 
  (
    SELECT AccountId
    FROM Opportunity
    WHERE CloseDate < Last_Week
  )

限制

  1. 在主语句的WHERE分句中,不能超过2INNOT IN语句
  2. 不能在半连接或者反连接前使用NOT操作符。若有这种情况,可以考虑把半连接转换为反连接,或者反连接转换为全连接
  3. 必须是Id字段或者外键,诸如... Where Account.Id IN (...)是非法的
  4. 子查询的查询字段必须与主查询对应的字段SObject一致,是且必须是对应的外键
  5. 子查询的字段条数不受限制,但是主查询条数仍收到限制
  6. 半连接或者反连接不能嵌套使用,即不能在半连接/反连接中再使用半连接或者反连接
  7. 子查询不能使用OR
  8. 子查询不支持COUNT, 'FOR UPDATE,ORDER BY,LIMIT`
  9. 下列对象不支持:
    • ActivityHistory
    • Attachments
    • Event
    • EventAttendee
    • Note
    • OpenActivity
    • Tags (AccountTag, ContactTag, and all other tag objects)
    • Task

详情可以查看SOQL and SOSL Reference以下章节:
Semi-Joins with IN and Anti-Joins with NOT IN

[LINK] Mutual Fund Explorer: A New Lightning Components Sample Application

original source: Mutual Fund Explorer: A New Lightning Components Sample Application

Highlight

  • Caching data with storable actions
  • Caching data with a custom cache
  • Creating a dropdown box from picklist values
  • Creating a dropdown box from a list of records
  • Event bubbling
  • Using application events
  • Using component events
  • Using a third-party JavaScript library
  • Using bound vs unbound expressions
  • Building admin-friendly components

Related Github repo: sfdx-dreaminvest

Use visualForce to add multiple records in Salesforce

The code is an improvement of this article.

  1. The main visualForce page AddmultipleAccounts code:
<apex:page controller="AddmultipleAccountsController">
<apex:form>
<apex:pageBlock title="Add multiple account" id="main_block">
<apex:pageBlockTable value="{!listAccount}" var="acc">
<apex:column headerValue="Account Name">
    <apex:inputField value="{!acc.Name}"/>
</apex:column>
<apex:column headerValue="Account Type">
    <apex:inputField value="{!acc.Type}"/>
</apex:column>
<apex:column headerValue="Industry">
    <apex:inputField value="{!acc.Industry}"/>
</apex:column>
    <!-- you can add more column here -->
</apex:pageBlockTable>
<apex:pageBlockButtons>
<apex:commandButton value="Add 1 Account Row" action="{!addAccount}" reRender="main_block"/>
<apex:commandButton value="Add 5 Account Rows" action="{!addAccounts}" reRender="main_block" />
<apex:commandButton value="Save Accounts" action="{!saveAccounts}" />
</apex:pageBlockButtons>
</apex:pageBlock>
</apex:form>
</apex:page>
  1. After insert the records, there will be a simple page to show the result, the page AllAccountsSaved will show the result, you can make more work on this page. the code:
<apex:page sidebar="false" showHeader="true">
<center>
    <h3> Congrats your accounts have been successfully saved! </h3>
</center>
</apex:page>
  1. Here the custom controller AddmultipleAccountsController code:
public with sharing class AddmultipleAccountsController {
    public list<Account> listAccount{get;set;}

    public AddmultipleAccountsController() {
        listAccount = new list<Account>();
        listAccount.add(new Account());
    }

    //add one account at a time
    public void addAccount() {
        listAccount.add(new Account());
    }

    //add five account at a time
    public void addAccounts() {
        for(Integer j=0; j < 5; j++) {
        listAccount.add(new Account());
        }
    }

    public PageReference saveAccounts() {
        try {
            insert listAccount;
        } catch(System.DmlException e) {
            for(Integer i=0; i < e.getNumDml(); i++) {
                System.debug(e.getDmlMessage(i));
            }
        }
        return Page.AllAccountsSaved;
    }
}
  1. A test method AddmultipleAccountsControllerTest for the custom controller above, code:
@isTest
private class AddmultipleAccountsControllerTest {

    static testMethod void testAddAccount() {
        Test.startTest();
        AddmultipleAccountsController aacontroller = new AddmultipleAccountsController();
        aacontroller.addAccount();
        list<Account> listAccount = aacontroller.listAccount;
        Test.stopTest();
        system.assert(listAccount.size() == 2);
    }

    static testMethod void testAddAccounts() {
        Test.startTest();
        AddmultipleAccountsController aacontroller = new AddmultipleAccountsController();
        aacontroller.addAccounts();
        list<Account> listAccount = aacontroller.listAccount;
        Test.stopTest();
        system.assert(listAccount.size() == 6);
    }

    static testMethod void testSaveAccounts() {
        Test.startTest();
        AddmultipleAccountsController aacontroller = new AddmultipleAccountsController();
        aacontroller.listAccount[0].Name = 'lushang test account';
        aacontroller.saveAccounts();
        Test.stopTest();
        Account[] acc = [SELECT id,name from Account where name = 'lushang test account'];
        system.assert(acc.size() == 1);
    }
}
  1. Create a visualForce Tab for the page, the user can use this tab to add multiple records.
  • You can change the tab permission settings in certain profile's "Object Settings"
  • You can translate the tab name in the Translation Workbench's translate bar, section is : "Web Tab"

Triggers and Order of Execution

This article if from developer.salesforce.com and you can see the source here

  1. Loads the original record from the database or initializes the record for an upsert statement.
  2. Loads the new record field values from the request and overwrites the old values.
    If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:
  • Compliance with layout-specific rules
  • Required values at the layout level and field-definition level
  • Valid field formats
  • Maximum field length
    When the request comes from other sources, such as an Apex application or a SOAP API call, Salesforce validates only the foreign keys. Prior to executing a trigger, Salesforce verifies that any custom foreign keys do not refer to the object itself.
    Salesforce runs user-defined validation rules if multiline items were created, such as quote line items and opportunity line items.
  1. Executes all before triggers.
  2. Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
  3. Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record is not saved and no further steps, such as after triggers and workflow rules, are taken.
  4. Saves the record to the database, but doesn't commit yet.
  5. Executes all after triggers.
  6. Executes assignment rules.
  7. Executes auto-response rules.
  8. Executes workflow rules.
  9. If there are workflow field updates, updates the record again.
  10. If the record was updated with workflow field updates, fires before update triggers and after update triggers one more time (and only one more time), in addition to standard validations. Custom validation rules, duplicate rules, and escalation rules are not run again.
  11. Executes processes.
    If there are workflow flow triggers, executes the flows.
    The Process Builder has superseded flow trigger workflow actions, formerly available in a pilot program. Organizations that are using flow trigger workflow actions can continue to create and edit them, but flow trigger workflow actions aren’t available for new organizations.
  12. Executes escalation rules.
  13. Executes entitlement rules.
  14. If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
  15. If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
  16. Executes Criteria Based Sharing evaluation.
  17. Commits all DML operations to the database.
  18. Executes post-commit logic, such as sending email.