A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.

New answers tagged

1

So -- if going the trigger route, consider decoupling the problem wherein Apex is used to derive keywords (because Apex has superior string handling tools to WFRs or PBs). Then use Case Assignment rules to work off the keywords. This gives you the best of both worlds - easily understandable and changeable assignment rules and deep parsing technology when ...


0

You need to use the WhatId in order to get the related cases. See my comments inline: Trigger CaseClosed on Task(Before Insert) { Set<Id> caseIds = new Set<Id>(); Set<Id> closeCaseIds = new Set<Id>(); //get all the case ids that are related to the new tasks for (Task t : Trigger.new) { if(t.WhatId != ...


3

You need to filter by the WhatId for the records. The ID you got was some random case in the database that was closed. Here's what you're looking for: trigger preventTaskOnClosedCase on Task (before insert) { Set<Id> caseIds = new Set<id>(); for(Task record: Trigger.new) { if(record.WhatId != null && record.WhatId....


0

Make sure the Log A Call action is added to the page layout in the 'Salesforce Mobile and Lightning Experience Actions' section


1

this is #spring20 know issue you can track it and work around also here Know issue


1

We have resolved this issue. In aura component or lwc, when we have a if we don't specify a recordTypeId we receive the error specified: An error occurred while trying to update the record. Please try again. Record Type ID: this ID value isn't valid for the user: 012000000000000AAA So if no recordTypeId was specified in the component an exception is ...


1

We are encountering the same issue with an aura component using the lightning:recordEditForm tags. Our prod environment is on Winter '20 and it works just fine but the sandboxes are Spring '20 and we get that exact error: An error occurred while trying to update the record. Please try again. Record Type ID: this ID value isn't valid for the user: ...


3

This could be an issue due to the Spring 20 Security update. This is documented here As per the update Access to user roles is available for users with the View Roles and Role Hierarchy permission. Editing user roles is available for users with the Manage Roles permission. So your rule might be breaking due to it. One solution i can think of is you ...


0

https://help.salesforce.com/articleView?id=000327515&type=1&mode=1 @Arnold Jr. brings up good suggestions. Above is the link to a Salesforce knowledge article regarding this. Two things to check based on the article. Check your "Verification" column in your email-to-case settings. Setup --> Email-to-case --> Routing Addresses If the ...


2

You do this with Auto-Response rules: https://help.salesforce.com/apex/HTViewHelpDoc?id=creating_auto-response_rules.htm Setup --> Case Auto-Response Rules You can check here to see if you have any existing rules. You can create a new rule and then rule entries. The entries act in an order and when the incoming case comes in it goes through these until it ...


Top 50 recent answers are included