function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Angel Montiel 6Angel Montiel 6 

I need some help with a trigger

Hi everyone:

I'm new at salesforce, and I want to create a trigger that sets an specific record type to a new created record.

For example, I have this two custom objects (Inspections and Recomendations), and the following record types for the Inspections Object:

-Mouse
-Grass
-Other

I'd like that when I create a new recomendation record, it should have the same record type as the one of its parent relation, in this case, the same record type as the Inspection record.

Thanks.
Amit Chaudhary 8Amit Chaudhary 8
Hi Angel Montiel 6,

I will recomend you to please check below trailhead module to learn about trigger. We can write code for you but it will better if you can start learning and start coding. IF you will get any error we will help to complete your trigger.
1) https://developer.salesforce.com/trailhead/module/apex_triggers

Also please check below post
Trigger Context Variables
1) http://amitsalesforce.blogspot.com/2015/10/trigger-context-variables.html

Trigger Best Practices | Sample Trigger Example | Implementing Trigger Framework
1) http://amitsalesforce.blogspot.com/2015/06/trigger-best-practices-sample-trigger.html

1) One Trigger Per Object
A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts

2) Logic-less Triggers
If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org. 

3) Context-Specific Handler Methods
Create context-specific handler methods in Trigger handlers

4) Bulkify your Code
Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time.

5) Avoid SOQL Queries or DML statements inside FOR Loops
An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception

6) Using Collections, Streamlining Queries, and Efficient For Loops
It is important to use Apex Collections to efficiently query data and store the data in memory. A combination of using collections and streamlining SOQL queries can substantially help writing efficient Apex code and avoid governor limits

7) Querying Large Data Sets
The total number of records that can be returned by SOQL queries in a request is 50,000. If returning a large set of queries causes you to exceed your heap limit, then a SOQL query for loop must be used instead. It can process multiple batches of records through the use of internal calls to query and queryMore

8) Use @future Appropriately
It is critical to write your Apex code to efficiently handle bulk or many records at a time. This is also true for asynchronous Apex methods (those annotated with the @future keyword). The differences between synchronous and asynchronous Apex can be found

9) Avoid Hardcoding IDs
When deploying Apex code between sandbox and production environments, or installing Force.com AppExchange packages, it is essential to avoid hardcoding IDs in the Apex code. By doing so, if the record IDs change between environments, the logic can dynamically identify the proper data to operate against and not fail

Let us know if this will help you
Thanks
Amit Chaudhary
Abhishek BansalAbhishek Bansal
Hi Angel,

Please use the below trigger code : 
trigger setRecordType on Recomendation__c (before insert){//replace Recomendation__c with the API name of Recomendations object
	Set<Id> inspectionIds = new Set<Id>();
	for(Recomendation__c recomend : trigger.new){//replace Recomendation__c with the API name of Recomendations object
		if(recomend.Inspection__c != null){//replace Inspection__c with the API name of Inspection loookup field on Recommendation object
			inspectionIds.add(recomend.Inspection__c);
		}
	}
	
	if(inspectionIds.size() > 0){
		Map<Id,Inspection__c> mapOfInspection = new Map<Id,Inspection__c>([Select RecordType.Name from Inspection__c where Id IN : inspectionIds]);
		for(Recomendation__c recomend : trigger.new){
			if(mapOfInspection.containsKey(recomend.Inspection__c)){
				recomend.RecordTypeId = Schema.SObjectType.Recomendation__c.getRecordTypeInfosByName().get(mapOfInspection.get(recomend.Inspection__c).RecordType.Name).getRecordTypeId();
			}
		}
	}
}


Please take care of the API name of the objects and fields and let me know if you face any issue with above code.

Thanks,
Abhishek Bansal