Hot answers tagged

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 ...


2

Do the followings: Create a separate layout for community users(if you don't have one yet). Remove the Change Record Type button from that page layout. Assign the layout to the community profile. Make the Record Type field read-only from the community users profile.


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 ...


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: ...


1

Your trigger is expecting exactly one row: some_object record = [select ... from ... where ... ]; But there's no results returned. Your trigger should not assume that there's exactly one row being returned. Three standard designs for this are as follows. Assign to List, use First Record some_object[] records = [select ... from ... where ...]; if(records....


1

Case assignment rules run synchronously within the DML transaction where they are "triggered" (e.g. Case insert/update where the DmlOptions header to run assignment rules) is set. This header is automatically set, for example, in Email-to-Case or Web-to-Case. See Triggers and Order of Execution Step 8 When the assignment rules run, they update the Case with ...


Only top voted, non community-wiki answers of a minimum length are eligible