Skip to main content

#Record Types2 人がディスカッション中

I have a flow that guides users through a manual lead conversion, when converting to an opportunity they are able to select the opportunity record type that they want to create.  However the flow will give them the option of every available opportunity record type, not just the ones they have permissions for.  Is there a declarative solution to this , to only show the ones they have permissions for, without using an apex class? 

 

#Flow  #Record Types  #Permissionset

1 件の回答
  1. 昨日、12:54

    Hi Carolyn - the catch is that RecordType is metadata every user can read, so a Get Records or Record Choice Set on RecordType always returns them all, regardless of who is assigned. There is no native 'filter record types by assignment' in Flow. Two routes that need no Apex you write or maintain: 

     

    1. UnofficialSF's 'User-Aware Record Type Picker for Flows' - a free installable screen component built for exactly this; it shows only the record types the running user is actually assigned. Cleanest option if you are OK installing a component. 

     

    2. Pure-native with Custom Permissions - create one Custom Permission per opportunity record type (or per group), assign each on the same permission set that grants that record type, then set each choice's component visibility (or a Decision) on the running user having that permission via Permission.YourCustomPermission. 100% declarative; the trade-off is you maintain the mapping, so it fits best when the record-type count is small. 

     

    Tip: also run the screen flow in User Mode so field/record access is enforced - just note User Mode will not filter the record-type list itself, since that is assignment, not record access. 

     

    If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

0/9000

Hey All! Looking for some fresh ideas regarding inter-group case ownership / management --

 

We currently have five different support groups in our org -- different record types, page layouts, queues, etc. Private sharing model, with some 'bandaid' case sharing rules so some of the groups can view other groups' cases. 

 

I'm just wondering how other companies with multiple groups of support users "play nice" if they need to transfer cases to each other? Right now, we instruct the agents to change the Case Owner field to the queue of the group that they want to send their case to. Because of this, we've had to make sure all of the groups can have some sort of permission to view or edit the other groups' record types / page layouts. 

 

How do you do it? 

 

We've been tasked to figure out a 'foolproof' way for an agent to successfully transfer a case to another group systematically rather than training to change Case Owner. Would you include changing the record type as well as the owner? Or leaving as same record type, but giving access for all groups to read / write the others' record types? 

 

Just looking for ideas!!!

4 件のコメント
  1. 2025年12月18日 16:40

    we use a screen flow - with a picklist for the team and then we can prefilter the new owner lookup by the team that they chose (we use public groups) -- when they hit save, we change the record type/entitlement/etc on the case for them

0/9000

Hi,

 

I am trying to create custom matching rules to identify duplicates . I want to include the record type field to restrict search accounts with same record type and unable to find an option. In my scenario there could be duplicate accounts in different teams with different record types and I want to throw duplicate error only if there exists an account with same name within the same record type.

 

I was unable to even add a matching criteria for a custom field. Please suggest how to resolve this.

 

Thank you,

Aruna

11 件の回答
  1. 2024年9月27日 2:00

    @Jesús Romo here are some comments:

    1. Duplicate Rule checking is initiated in the background every time you create or update duplicate rules.  This covers the retrofit of existing records, but take heed: it runs in the background and with a large database can take quite some time to complete.
    2. Default field values are assigned before the field is displayed in the UI.  The documentation doesn't say at what point this value is saved when the record is created without UI, but I guess it would be after all automations are run (pre and post save), if no value is assigned to that field.
    3. What I understand from your comment is that you have two separate requirements: (a) to ensure a single account has no more that one of each address type, and (b) that the Address object has no duplicate records.  Is that correct?  For (a), you could create a record-triggered flow on Address object, which counts the different address records for an account and checks there for duplicates, displaying a custom error message if the user is trying to break the rule.  This would only work for new and changed address records, of course, so you'd need a way to review existing accounts. For (b) you can create a matching rule on Address, using the important (up to 5) fields such as Address Type, City (Fuzzy), ZIP (Fuzzy), State/Province, Country, then use this for a new Duplicate Rule.  Once you activate the rule, this will allow you to create a report type for Addresses with Duplicates.
0/9000

🌤 Introducing Record Types: they allow you to have different business processes, picklist values, and page layouts to different users based on profile.

 

Check out the video linked ⬇️  to learn more!

Record Types

2 件のコメント
0/9000

Hi all,

 

any ideas on how to best manage duplicate accounts ? Users engage with the same organisations in very different ways and therefore capture very different information. The confusion is obviously people seeing the same type of organisation that does not apply to them. 

 

What you recommend to manage this ?

 

#Duplicate Management  #Standard Duplicate Rules  #Record Types

2 件の回答
  1. 2024年4月9日 14:40

    Hi,

     

    @Ezugo Okoma I am working with something similar to this. We have 4 different lines of business. A single customer may have 2, 3, or 4 lines of business. This means they may have that many different Accounts. We are in a cleanup process right now in an attempt to make this a cleaner environment.

     

    I now have a Parent Record type/Record page. That page can have whatever base information you want, Name, Address, phone, etc...

     

    The Users will attach each of the existing Accounts to the Parent (via the Parent Account Field) to make a connection. They can click on the hierarchy of any of the Accounts to see what they are related to. 

     

    In a step further I created a flow to link the Accounts/Opportunities/Contacts as actual related lists to the Parent. If they open just the Parent record they can view the related lists and see everything at a glance. 

     

    I know this is an older post but I hope this helps. 

0/9000

I have 5 record types for the opportunity object. I know when you first create a record type, you can select which profiles have visibility. I am trying to go back and edit the visibility so not all profiles have visibility on all record types but only the ones they need to see. How do I do this? When I click "edit" the visibility checklist does not appear.

 

#Sales Cloud  #Record Types

2 件の回答
0/9000

Hi,

I am getting this error when I try to hit the button for inline editing in the Task List View. I had been using Record Types for Tasks but deleted the records types. Now there are no record types being used on the Task Object. How do I get rid of this error? 

 

#Salesforce  #List Views  #Record Types

1 件の回答
  1. 2024年2月22日 21:12

    Hi @Jenna Weltz,

     

    1. f an object's record types are all in "Inactive" status, inline editing won’t work for the affected records. To resolve this issue:
    • Delete all inactive record types for that object
    • Update your record types so that there is at least one active record type                      

    Note: This 'active' record type doesn’t need to be assigned to any profiles. 

     

    • After this is done, add the list view filter "Record Type EQUALS <blank>" 

    For more details pls check

    https://help.salesforce.com/s/articleView?id=000384838&type=1 

     

    Thanks

0/9000

I made a new case record type named at risk. I also made a new page layout named at risk. I assigned the new at risk page layout to the new at risk record type. When I log in with my tech support app in lightning I see the old page layout when I select the At risk record type when making a new case, but when I log into the sales app I do see the new page layout when making a new at risk case. How do i get the new at risk page layout to show up when you create a new at risk case from the tech support app in Salesforce

 

 

#Record Types #Sales Cloud

2 件の回答
  1. 2024年2月22日 20:21

    When I am in the sales app and I click new to create a new case and I select the at risk record type I see the new at risk page layout. When I'm in the Technical Support app and I click new to create a new case and I select the at risk record type I see the layout assigned to the TS page layout.

    How do I fix this so that when I'm in the Technical Support app and I click the new button to create a new case and I select the at risk record type I see the at risk page layout?

    I can see the Technical Support app but I dont see where to include the new At risk things.

0/9000

I am using the Account Contact Relationship object to define the role each contact has with the account. The account can be a record type of Shop Account or Customer Account. Depending on the record type of the Account, only specific values in the roles multi-select picklist field of the related list (Account Contact Relationship) should display:

 

Shop Account: Owner, Manager, Provider

Customer Account: Owner, Driver, Dispatcher

 

What are my options for accomplishing this? For this use case, what is the best option?

 

#Picklist Dependency  #Dependent Picklist Relationships  #Record Types

2 件の回答
  1. 2024年2月21日 20:11

    @Caleb Markovich,

     

    This won't be possible declaratively.

    You will have to opt for custom LWC/Aura component along with an Apex class.

0/9000

[9:15 AM] Andriehet Smit

 

Good day 

 

I created a queue where the default record type is "Internal record type." We are, however, attempting to change the record type to a custom record type. The cases for this queue generates once an opportunity is closed/won. I have done the auto-assignment rule and updated the existing page layout assignment to no avail. Are you able to advise how we can change the record, please?

 like 1

 

#Record Types

5 件の回答
  1. 2024年2月19日 12:11

    Thank you for the reply 

     

    We managed to fix the issue 

0/9000