-
How to solve "Registration accountId parameter value is not valid" error in Salesforce community cloud?
How to solve the error "Registration accountId parameter value is not valid" in self registration process in Salesforce?
-
1 Reply
-
Hi Shraddha,
By going through some sites I found this-
- You need to add the “Allow Customer Portal Self-Registration field to the layout that is tied to the user profile you are using to create this contact
- Make sure FLS is visible for this field for the user profile you are using to create this contact
- Edit your contact and set this flag
Hope this helps.
-
This reply was modified 7 years, 11 months ago by
shariq.
Log In to reply.
Popular Salesforce Blogs
The Salesforce Schema Builder — What You Need To Know
Keeping the pace of change is a constant challenge for systems and IT teams running Salesforce. Luckily, the platform comes with a ton of built-in…
Power Play: Mastering Salesforce Integration Patterns And Practices
Ready to turbocharge your Salesforce experience? In our hyper-connected global village, just owning Salesforce isn't enough. You need seamless integration with data, systems, and processes…
Email Service-Inserting Data in Salesforce using Email Attachment
Force.com provides us powerful and secure functionality for sending and receiving emails. We can execute our apex logic whenever we receive an email. By using…
Popular Salesforce Videos
Salesforce Validation Rules - Keep your Data Clean
Watch this short video for just over 2 minutes and learn how to keep your Salesforce data clean? The answer is simple: Use field validation…
Difference between Workflow Rules and Process Builder in Salesforce
This video explains the difference between workflow rules and process builder. It is divided into four parts : 1. When to use Workflow 2. When…
TrailheaDX '18 Opening Keynote - Part 6: Skill Up Everyone
Related Videos: Salesforce TrailheaDX ’18 Opening Keynote – Part 1: Create Connected Customer Experiences TrailheaDX ’18 Opening Keynote – Part 2: Salesforce Platform TrailheaDX ’18…
