Assign different record types to different users of the same profile - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Saurabh KherSaurabh Kher 

Assign different record types to different users of the same profile

Is there a way to assign different record type of case object to different users having same profile. I have a requirement to show department specific picklist values on case object's when specific department user logs in and try to create new case. All department falls under same profile I am not thinking of creating separate profile for each department.

**So the requirement is:** If User U1 of Department D1 having profile R logs in, he should see only R1 record type of case object. But when User U2 or Department D2 or same profile R logs in, he should see only R2 record type of case object. It will apply for other department as well.

**What I have done so far:** 1. Created record types and assigned all record type to Profile R. There will be one record type as default because there is no option to disable default option. User in this case getting option to select one record type but values are coming from default record type only.
2. Created permission set for each department and removed all record type from profile level and assigned to specific permission set. Then assigned specific permission set to one user at a time. In this case record type selection option is not appearing but values are from master record type which is default in case of no record type.

**How can I disable default record type since values are coming from default only**

Any suggestion in this case much appreciated.
Amnon KruviAmnon Kruvi
Hi Saurabh,

When users only have access to a single record type, the system does not offer them the choice to select a record type and assigns the one that they can use. They can then only select picklist options from that record type.

By your description, it sounds like your users are assigned the Master record type, which shouldn't be the case. You'll want to verify a few things:
1. Are your record types activated?
2. Does the permission set have the record type enabled?
3. Is the permission set assigned to the user who is seeing the master values?
Saurabh KherSaurabh Kher
Hi Amnon,
Thanks for the reply
To answer your questions:
1. Are your record types activated? - Yes
2. Does the permission set have the record type enabled? - Yes, assigned one record type to one permission set
3. Is the permission set assigned to the user who is seeing the master values? - yes, even after assigning specific permission set, user can see values of master record type since that is set default automatically by the system.
Amnon KruviAmnon Kruvi
OK. What happens when you assign a single record type to the profile?
Saurabh KherSaurabh Kher
Then it populates values from that record type only. And default record type also changes.
Amnon KruviAmnon Kruvi
Thanks. In this case I would like you to triple check that the permission set has the record types enabled and that it is assigned to the user. You can see how the system behaves when a user has access to a record type, so the issue you are describing can only be explained by the user not having access to any record types.
Saurabh KherSaurabh Kher
As per this page,
https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/permissions_record_type_access.htm

if master is set at profile and only one record type at permission set then records from permission set should appear. But record from master is appearing here. See attachment.

Profile Setting
At profile level

Permission Set:
At permission set

User Access:
User Assignment
Amnon KruviAmnon Kruvi
I agree with you that this is how it should work. You wouldn't happen to have two permission sets with the same name, by any chance?
Saurabh KherSaurabh Kher
No, right now I have created only 2 persmission sets to test functionality. So same name record is not there. Also we have built custom lightning component for case creation and using that one. Not standard case creation. Is there anything missing here ?
Amnon KruviAmnon Kruvi
Interesting. If you're using a custom lightning component for case creation it could be that it's smart enough to look at profile settings, but not permission sets. What happens if you deactivate the custom override and try it with a standard page?
Saurabh KherSaurabh Kher
That i have to check. Just trying this one for cutom lightning component.