Salesforce中使用PersonalAccount的相关经验汇总(Admin+DeveloperApexTrigger)

【前言】&＃xff1a;

早前接触到Personal Account的时候仅仅认识到Enable Personal Account后&＃xff0c;从Account Tab创建Account时就多了一个Personal Account的记录类型&＃xff0c;同时创建一条Personal Account记录后随之copy了一份记录到Contact&＃xff0c;如果在任意端Account/Contact改了这个Personal Account&＃xff0c;两边信息都是同步的。

【问题】&＃xff1a;

基于提到的上文你可能产生与我相同的疑问&＃xff1a;既然Personal Account里面有内部同步机制确保Account和Contact对像记录是一样的&＃xff0c;那么我是不是在任意一个对象上写一个Trigger就能保证两个对象都有相同的效果呢&＃xff1f;

【解惑】&＃xff1a;

1. Business Case&＃xff1a;
假如需求是这样的&＃xff1a;如果Personal Account的Email里面包含test文本&＃xff0c;我们就将改Email值变为invalid&＃64;email.com&＃xff1b;

2. Test Case1&＃xff1a;在Account上写一个Trigger如下&＃xff1a;

trigger TestAccountTrigger on Account(before insert, before update) {for(Account acc : (List)Trigger.New) {if(acc.PersonEmail.contains(&＃39;test&＃39;)) {acc.PersonEmail &＃61; &＃39;invalid&＃64;email.com&＃39;;}}
}

我们先注释Code片段&＃xff0c;创建一条如下记录&＃xff0c;会观察到两条记录页面布局都一样&＃xff0c;区别是&＃xff1a;
a、ID不同&＃xff0c;一个前缀是001&＃xff08;Account&＃xff09;&＃xff0c;一个是003&＃xff08;Contact&＃xff09;&＃xff1b;
b、如果我们从第二幅图中点击右边的View Fields&＃xff0c;此时打开的对象是Account Fields&＃xff0c;而非Contact Fields&＃xff1b;


随后我们解注刚注释掉的Trigger片段&＃xff0c;再次在任意端修改记录&＃xff0c;会发现两边记录依然保持同步。

3. Test Case2&＃xff1a;在Contact上写一个Trigger如下&＃xff1a;

trigger TestContactTrigger on Contact(before insert, before update) {for(Contact con : (List)Trigger.New) {if(con.Email.contains(&＃39;test&＃39;)) {con.Email &＃61; &＃39;invalid&＃64;email.com&＃39;;}}
}

这时我们先将Email改成不包含test的任意Email格式文本&＃xff0c;随后再重新编辑为包含test文本的Email&＃xff0c;你会发现&＃xff0c;你在Contac上写的Trigger没生效。

4. 上面的内容咱们先放一放&＃xff0c;先看一下下边这个图&＃xff0c;来增加你对Personal Account的神秘感&＃xff1a;


你不难发现神奇的是&＃xff0c;用API Name查看插件显示的Email和Phone竟然不一样&＃xff01;&＃xff01;&＃xff01;

【总结】&＃xff1a;

1. 对于Personal Account标准字段的同步&＃xff0c;Trigger仅需写在Account上即可&＃xff1b;
2. Personal Account其实在元数据中是一个包含在Account子节点的标准的单独的对象&＃xff0c;一旦开启&＃xff0c;会导致Account Fields发生变化&＃xff0c;Contact Field无影响&＃xff0c;这时Personal Account的记录类型自然会叠加在Account记录类型上&＃xff1b;
3. 创建一条Personal Account记录相当于一条记录被不同ID&＃xff08;AccountID / ContactID&＃xff09;所指向&＃xff1b;

【注意事项】&＃xff1a;

1. 截至20年11月11日&＃xff0c;无法通过提Case给SF Support的方式开启Person Accounts&＃xff0c;详见Idea Details —— Ability to log a case using Developer Org for Support (First Class Citizen)&＃xff1b;
2. 关于记录合并 - Person accounts can be merged only with other person accounts. You can’t merge person accounts that are enabled as portal or community users&＃xff1b;
3. 关于自动化触发 - Creating or editing a person account triggers Process Builder processes. Creating or editing a person account triggers account workflow rules&＃xff1b;
4. 关于Lead转化 - Leads that don&＃39;t have a value in the Company field are converted to person accounts. Leads that do have a value in the Company field are converted to business accounts&＃xff1b;
5. In Lightning Experience, you can send list emails to person accounts from Contact list views but not Account list views&＃xff1b;
6. 关于List View - An admin can show which records are person accounts by adding the Is Person Account field to the list of fields to display. To include or exclude person accounts from a list view, add the Is Person Account field to the filter criteria&＃xff1b;
7. 关于合并字段 - You can use the merge field {!Account.IsPersonAccount} to determine whether you are working with a person account or a business account&＃xff1b;