#Record Types3 diskutieren mit

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

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

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. 

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

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.