#Triggers6 discussing

Your trigger is most likely firing fine. The catch is the Upload Files dialog on the related list doesn't show the text from addError on ContentVersion, it just replaces it with its own generic "Can't upload" message. You can confirm by turning on a debug log for your user and uploading a file with a long name, your message should show up in the log. 

If blocking isn't a hard requirement, an easier route is to shorten the name in the same before insert instead of throwing an error, so the upload just goes through:

if (file.Title != null && file.Title.length() > MAX_CHAR_LIMIT) { 

    file.Title = file.Title.left(MAX_CHAR_LIMIT); 

} 

Title doesn't include the extension (that's on PathOnClient / FileExtension), so the file still opens normally. If you do need to block it, it's probably worth adding a note near the related list so users know about the 80 character limit, since they won't see your custom text.

Hi Naveen, 

Check the following things, 

API User Permissions: Verify that the integration user has the necessary permissions to trigger the logic. 

Integration Method: Ensure the API method used (like create, update) aligns with your trigger logic. 

please mark this answer helpful if it solved your query.

Arun Goel

Oct 1, 2024, 7:40 PM

Hi Naveen, 

Check the following things, 

API User Permissions: Verify that the integration user has the necessary permissions to trigger the logic. 

Integration Method: Ensure the API method used (like create, update) aligns with your trigger logic. 

please mark this answer helpful if it solved your query.

Arun Goel

Oct 1, 2024, 7:40 PM

Hi Naveen, 

Check the following things, 

API User Permissions: Verify that the integration user has the necessary permissions to trigger the logic. 

Integration Method: Ensure the API method used (like create, update) aligns with your trigger logic. 

please mark this answer helpful if it solved your query.

Hello @Swati Patle

You can take reference from below code.

Trigger TotalOpportunityAmount on Opportunity (after insert,after update,after delete,after undelete ) {
    List<Account> oppListToIterate = Trigger.isDelete ? Trigger.old : Trigger.New;
    List<Account> accountListToUpdate = new List<Account>();
    set<Id> accountIds=new set<Id>();
    for(Opportunity opp:oppListToIterate){
        if((Trigger.isInsert || Trigger.isDelete) && opp.ExpectedRevenue != null )
        	accountIds.add(opp.accountID);
        else if(Trigger.isUpdate && (opp.ExpectedRevenue != Trigger.oldMap.get(opp.Id).ExpectedRevenue)){
            accountIds.add(opp.accountId);
        }
	else if(Trigger.isUpdate && (opp.AccountId != Trigger.oldMap.get(opp.Id).AccountId)){
            accountIds.add(opp.accountId);
            accountIds.add(Trigger.oldMap.get(opp.Id).accountId);
        }
    }
    for(AggregateResult ar : [SELECT AccountId AcctId,SUM(ExpectedRevenue) totalRevenue FROM Opportunity WHERE AccountId in :accountIds group by AccountId]){
        accountListToUpdate.add(
        	new Account(
            	Id = (Id) ar.get('AcctId'),
                TotalRevenue__c = (Integer) ar.get('totalRevenue');
            )
        );
    }  
    if(!accountListToUpdate.isEmpty())
	UPDATE accountListToUpdate;	
}

In case you find any other issue please mention. 

If you find your Solution then mark this as the best answer. 

Hii,

It's better if you share the approach you followed.

However, you can use something like this in your trigger handler

 //You can fetch the user Ids through query and use them instead of hardcoding

 Id userAId = 'xxxxxxxxxxxx'; // User A's Salesforce ID

 Id userBId = 'xxxxxxxxxxxx'; // User B's Salesforce ID

 // Loop through all the Case records being inserted

 for (Case newCase : Trigger.new) {

 // Check the 'Type' field to determine which user should be assigned

 if (newCase.Type == 'Technical Support') {

 newCase.OwnerId = userAId; // Assign to User A

 } else if (newCase.Type == 'Billing') {

 newCase.OwnerId = userBId; // Assign to User B

 } else {

 // newCase.OwnerId = defaultUserId;

 }

 }

Hi,

The trigger prevents the deletion of a Case record if it is associated with both an Account and a Contact. Before the record is deleted, the trigger checks whether the Case has non-null values for both the AccountId and ContactId. If both are present, the trigger calls addError() on the Case record, which stops the deletion and displays an error message to the user, indicating that the Case cannot be deleted because it is linked to both an Account and a Contact.

The issue in your code is semicolon after for loop,the code should be :

trigger CaseDeleted on Case (before delete) {

// Loop through each case in the trigger's old context (cases that are being deleted)

for (Case cs : Trigger.old) {

// Check if both AccountId and ContactId are populated

if (cs.AccountId != null && cs.ContactId != null) {

// If the case is related to both an Account and a Contact, throw an error to prevent deletion

cs.addError('Cannot delete case related to both an Account and a Contact.');

}

}

}

Mark this helpful if it solves your query!

Hi Swati,

Try this:

trigger PreventLowAnnualRevenue on Account (before insert, before update) {

// Iterate through each Account record in the trigger context

for (Account acc : Trigger.new) {

// Check for insert operation

if (Trigger.isInsert) {

// Prevent insert if AnnualRevenue is less than $50,000

if (acc.AnnualRevenue != null && acc.AnnualRevenue < 50000) {

acc.addError('Annual Revenue cannot be less than $50,000.');

}

}

// Check for update operation

if (Trigger.isUpdate) {

// Prevent update if AnnualRevenue is being set below $50,000

Account oldAcc = Trigger.oldMap.get(acc.Id);

if (acc.AnnualRevenue != oldAcc.AnnualRevenue && acc.AnnualRevenue < 50000) {

acc.addError('Annual Revenue cannot be set to less than $50,000.');

}

}

}

}

Mark this helpful if it solves your query!

OK While you are creating CSV you must be careful about these things in your data:

- Comma inside data

- New line and Line feed values.

As well as I see you are only assigning   Database.query results as CSV, you should do in loop and control the values inside fields.

 SObject[] singleObjDataStorages = Database.query('SELECT ' + singleObjDataStorage.Fields_api_name_of_selected_object__c + ' FROM ' +System.label.SObject_Name );

Hi @Adarsh Agrawal,

Please refer to the documentation below.

Triggers and Order of Execution | Apex Developer Guide | Salesforce Developers

1. Salesforce performs different validation checks depending on the type of request.
   • For requests from a standard UI edit page, Salesforce runs these system validation checks on the record:
     • Compliance with layout-specific rules
     • Required values at the layout level and field-definition level
     • Valid field formats
     • Maximum field length
   • Additionally, if the request is from a user object on a standard UI edit page, Salesforce runs custom validation rules.
   • For requests from multiline item creation such as quote line items and opportunity line items, Salesforce runs custom validation rules.
   • For requests from other sources such as an Apex application or a SOAP API call, Salesforce validates only the foreign keys and restricted picklists. Before executing a trigger, Salesforce verifies that any custom foreign keys don’t refer to the object itself.
2. Executes record-triggered flows that are configured to run before the record is saved.
3. Executes all before triggers.
4. Runs most system validation steps again, such as verifying that all required fields have a non-null value and runs any custom validation rules.

Please check the fourth point.

Thanks!