Contact trigger to limit an account to not have more than 2 contactsAccount Roll up of contacts meeting certian criteriaTrigger on AccountAfter Update Trigger on Account to create contactPreventing duplicate records from being processed by triggerProcess more than 50K records in triggerI don't know the rest logic how to add both contacts amount and display it accountHow to create Account,Contact records based on the web-case data if contact email not existed in system?How can I have the contact record detail page reflect total accountHow to set ParentID field on Account record related to contact in a Trigger?update a field on contact once i associate a account
The qvolume of an integer
Why would Lupin kill Pettigrew?
Can I ask a publisher for a paper that I need for reviewing
Does nuclear propulsion applied to military ships fall under civil or military nuclear power?
How does increase in volume change the speed of reaction in production of NO2?
Asking bank to reduce APR instead of increasing credit limit
Can you dispel the Slow effect of a Stone Golem?
Can a non-EU citizen travel freely within the Schengen area without passport?
Starting VLC from command line always puts the window behind other windows
What is a simple, physical situation where complex numbers emerge naturally?
Applicants clearly not having the skills they advertise
Is a hash a zero-knowledge proof?
Why were the Night's Watch required to be celibate?
The oldest tradition stopped before it got back to him
When was the word "ambigu" first used with the sense of "meal with all items served at the same time"?
Are there mythical creatures in the world of Game of Thrones?
Where can I find the list of all tendons in the human body?
What is the intuition behind uniform continuity?
How to properly maintain eye contact with people that have distinctive facial features?
Strange math syntax in old basic listing
The most awesome army: 80 men left and 81 returned. Is it true?
Is this light switch installation safe and legal?
Rotated Position of Integers
Why use water tanks from a retired Space Shuttle?
Contact trigger to limit an account to not have more than 2 contacts
Account Roll up of contacts meeting certian criteriaTrigger on AccountAfter Update Trigger on Account to create contactPreventing duplicate records from being processed by triggerProcess more than 50K records in triggerI don't know the rest logic how to add both contacts amount and display it accountHow to create Account,Contact records based on the web-case data if contact email not existed in system?How can I have the contact record detail page reflect total accountHow to set ParentID field on Account record related to contact in a Trigger?update a field on contact once i associate a account
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Yesterday I got rejected from a job interview because the interviewer asked me to write a trigger to limit the number of contacts per account and I wrote exactly the below but he said this won't work and it is not the correct way to write the same.
I ran the same and it is working fine I am not able to see any problem with the below code can someone please help me understand from the interview's perspective why he said this is not the right way.
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
if(Trigger.operationType == triggerOperation.AFTER_INSERT
apex trigger
add a comment |
Yesterday I got rejected from a job interview because the interviewer asked me to write a trigger to limit the number of contacts per account and I wrote exactly the below but he said this won't work and it is not the correct way to write the same.
I ran the same and it is working fine I am not able to see any problem with the below code can someone please help me understand from the interview's perspective why he said this is not the right way.
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
if(Trigger.operationType == triggerOperation.AFTER_INSERT
apex trigger
add a comment |
Yesterday I got rejected from a job interview because the interviewer asked me to write a trigger to limit the number of contacts per account and I wrote exactly the below but he said this won't work and it is not the correct way to write the same.
I ran the same and it is working fine I am not able to see any problem with the below code can someone please help me understand from the interview's perspective why he said this is not the right way.
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
if(Trigger.operationType == triggerOperation.AFTER_INSERT
apex trigger
Yesterday I got rejected from a job interview because the interviewer asked me to write a trigger to limit the number of contacts per account and I wrote exactly the below but he said this won't work and it is not the correct way to write the same.
I ran the same and it is working fine I am not able to see any problem with the below code can someone please help me understand from the interview's perspective why he said this is not the right way.
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
if(Trigger.operationType == triggerOperation.AFTER_INSERT
apex trigger
apex trigger
edited Apr 14 at 6:01
sanket kumar
3,9792528
3,9792528
asked Apr 14 at 4:56
gs650xgs650x
308212
308212
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
This is the best example to use child soql to handle bulky records..
Please see the Below logic..
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
add a comment |
This trigger is not bulkified. It can't handle more than one account at a time. To fix the problem, an aggregate query would have been the most efficient solution. Here's my version of this trigger:
trigger BlockMoreThan2ContactOnAccount on Contact (after insert, after update, after undelete)
Set<Id> accountIds = new Set<Id>();
for(Contact record: Trigger.new)
accountIds.add(record.AccountId);
accountIds.remove(null);
Set<Id> morethan2Contacts = new Map<Id, AggregateResult>([
SELECT AccountId Id
FROM Contact
WHERE AccountId = :accountIds
GROUP BY AccountId
HAVING COUNT(Id) > 2]).keySet();
for(Contact record: Trigger.new)
if(moreThan2Contacts.contains(record.AccountId))
record.AccountId.addError('You may not have more than 2 contacts per account.');
You should always look for opportunities to use aggregate results (such as summing, counting, and finding averages) for performance reasons.
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
add a comment |
I would recommend creating a developer account to test said code with some debug statements to see what the output is.
Your soql query returns the total number of contacts in each account. This will work if there is only one account in the org, But it won't if there're more.Example: if there are 3 accounts with 4 contacts each, the output of contactListCount will be 12.
Also, in your 2nd loop you are looping again over Trigger.new, even if you did manage to filter out the accounts with 2+ contacts and added them to a new list, you ignored it by running over Trigger.new again and not over the new list.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f257764%2fcontact-trigger-to-limit-an-account-to-not-have-more-than-2-contacts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is the best example to use child soql to handle bulky records..
Please see the Below logic..
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
add a comment |
This is the best example to use child soql to handle bulky records..
Please see the Below logic..
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
add a comment |
This is the best example to use child soql to handle bulky records..
Please see the Below logic..
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
This is the best example to use child soql to handle bulky records..
Please see the Below logic..
trigger ContactTrigger on Contact (after insert, before Insert, before update, after update)
edited Apr 14 at 11:19
answered Apr 14 at 8:30
sarvesh kumarsarvesh kumar
10218
10218
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
add a comment |
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
Thank you for responding but what if the account query fetch more than 50K records
– gs650x
Apr 14 at 10:37
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
For that case, you can use where clause in soql to store accountid in the set. I update the answer, Please have a look
– sarvesh kumar
Apr 14 at 11:20
add a comment |
This trigger is not bulkified. It can't handle more than one account at a time. To fix the problem, an aggregate query would have been the most efficient solution. Here's my version of this trigger:
trigger BlockMoreThan2ContactOnAccount on Contact (after insert, after update, after undelete)
Set<Id> accountIds = new Set<Id>();
for(Contact record: Trigger.new)
accountIds.add(record.AccountId);
accountIds.remove(null);
Set<Id> morethan2Contacts = new Map<Id, AggregateResult>([
SELECT AccountId Id
FROM Contact
WHERE AccountId = :accountIds
GROUP BY AccountId
HAVING COUNT(Id) > 2]).keySet();
for(Contact record: Trigger.new)
if(moreThan2Contacts.contains(record.AccountId))
record.AccountId.addError('You may not have more than 2 contacts per account.');
You should always look for opportunities to use aggregate results (such as summing, counting, and finding averages) for performance reasons.
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
add a comment |
This trigger is not bulkified. It can't handle more than one account at a time. To fix the problem, an aggregate query would have been the most efficient solution. Here's my version of this trigger:
trigger BlockMoreThan2ContactOnAccount on Contact (after insert, after update, after undelete)
Set<Id> accountIds = new Set<Id>();
for(Contact record: Trigger.new)
accountIds.add(record.AccountId);
accountIds.remove(null);
Set<Id> morethan2Contacts = new Map<Id, AggregateResult>([
SELECT AccountId Id
FROM Contact
WHERE AccountId = :accountIds
GROUP BY AccountId
HAVING COUNT(Id) > 2]).keySet();
for(Contact record: Trigger.new)
if(moreThan2Contacts.contains(record.AccountId))
record.AccountId.addError('You may not have more than 2 contacts per account.');
You should always look for opportunities to use aggregate results (such as summing, counting, and finding averages) for performance reasons.
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
add a comment |
This trigger is not bulkified. It can't handle more than one account at a time. To fix the problem, an aggregate query would have been the most efficient solution. Here's my version of this trigger:
trigger BlockMoreThan2ContactOnAccount on Contact (after insert, after update, after undelete)
Set<Id> accountIds = new Set<Id>();
for(Contact record: Trigger.new)
accountIds.add(record.AccountId);
accountIds.remove(null);
Set<Id> morethan2Contacts = new Map<Id, AggregateResult>([
SELECT AccountId Id
FROM Contact
WHERE AccountId = :accountIds
GROUP BY AccountId
HAVING COUNT(Id) > 2]).keySet();
for(Contact record: Trigger.new)
if(moreThan2Contacts.contains(record.AccountId))
record.AccountId.addError('You may not have more than 2 contacts per account.');
You should always look for opportunities to use aggregate results (such as summing, counting, and finding averages) for performance reasons.
This trigger is not bulkified. It can't handle more than one account at a time. To fix the problem, an aggregate query would have been the most efficient solution. Here's my version of this trigger:
trigger BlockMoreThan2ContactOnAccount on Contact (after insert, after update, after undelete)
Set<Id> accountIds = new Set<Id>();
for(Contact record: Trigger.new)
accountIds.add(record.AccountId);
accountIds.remove(null);
Set<Id> morethan2Contacts = new Map<Id, AggregateResult>([
SELECT AccountId Id
FROM Contact
WHERE AccountId = :accountIds
GROUP BY AccountId
HAVING COUNT(Id) > 2]).keySet();
for(Contact record: Trigger.new)
if(moreThan2Contacts.contains(record.AccountId))
record.AccountId.addError('You may not have more than 2 contacts per account.');
You should always look for opportunities to use aggregate results (such as summing, counting, and finding averages) for performance reasons.
answered Apr 14 at 13:55
sfdcfoxsfdcfox
272k14220472
272k14220472
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
add a comment |
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
Thank you so much, I will always keep this in mind
– gs650x
Apr 14 at 16:47
add a comment |
I would recommend creating a developer account to test said code with some debug statements to see what the output is.
Your soql query returns the total number of contacts in each account. This will work if there is only one account in the org, But it won't if there're more.Example: if there are 3 accounts with 4 contacts each, the output of contactListCount will be 12.
Also, in your 2nd loop you are looping again over Trigger.new, even if you did manage to filter out the accounts with 2+ contacts and added them to a new list, you ignored it by running over Trigger.new again and not over the new list.
add a comment |
I would recommend creating a developer account to test said code with some debug statements to see what the output is.
Your soql query returns the total number of contacts in each account. This will work if there is only one account in the org, But it won't if there're more.Example: if there are 3 accounts with 4 contacts each, the output of contactListCount will be 12.
Also, in your 2nd loop you are looping again over Trigger.new, even if you did manage to filter out the accounts with 2+ contacts and added them to a new list, you ignored it by running over Trigger.new again and not over the new list.
add a comment |
I would recommend creating a developer account to test said code with some debug statements to see what the output is.
Your soql query returns the total number of contacts in each account. This will work if there is only one account in the org, But it won't if there're more.Example: if there are 3 accounts with 4 contacts each, the output of contactListCount will be 12.
Also, in your 2nd loop you are looping again over Trigger.new, even if you did manage to filter out the accounts with 2+ contacts and added them to a new list, you ignored it by running over Trigger.new again and not over the new list.
I would recommend creating a developer account to test said code with some debug statements to see what the output is.
Your soql query returns the total number of contacts in each account. This will work if there is only one account in the org, But it won't if there're more.Example: if there are 3 accounts with 4 contacts each, the output of contactListCount will be 12.
Also, in your 2nd loop you are looping again over Trigger.new, even if you did manage to filter out the accounts with 2+ contacts and added them to a new list, you ignored it by running over Trigger.new again and not over the new list.
edited Apr 14 at 11:21
answered Apr 14 at 6:17
JsonJson
447627
447627
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f257764%2fcontact-trigger-to-limit-an-account-to-not-have-more-than-2-contacts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown