+ Start a Discussion
Samy.SaiedSamy.Saied 

Superbadge: Lightning Experience Rollout Specialist - Issue on Item 4

I keep getting an error on Item #4 "The custom set of fields that are highlighted on account records must be assigned to the required profile."

The requirement is asking for having highlights based on profiles, but as we know compact layouts are applied to the whole system not by profile.

I am not sure how to fix this, any help is appreciated.
Best Answer chosen by Samy.Saied
Samy.SaiedSamy.Saied
@Carl That is exactly what I did, but the issue is that the requirement want to assign a different compact layout per profile, and the only way to do that is by assigning different record type to the corresponding profile.

Apparently in order to pass this question you have create the record type although I am not convinced that because one user in the org want to use it differently, I would create him a different record type considering this can be done in many other ways like grouping the fields he is interested in to the top of the page in a section. Creating a whole new record type sort of limit the other users from different profiles use the same accounts and see their highlights.

I believe this requirement is badly worded.

All Answers

Carl Brundage (Dev)Carl Brundage (Dev)
Check out the Tip at the bottom of this Trailhead module - https://trailhead.salesforce.com/modules/lex_customization/units/lex_customization_compact_layouts
Samy.SaiedSamy.Saied
@Carl That is exactly what I did, but the issue is that the requirement want to assign a different compact layout per profile, and the only way to do that is by assigning different record type to the corresponding profile.

Apparently in order to pass this question you have create the record type although I am not convinced that because one user in the org want to use it differently, I would create him a different record type considering this can be done in many other ways like grouping the fields he is interested in to the top of the page in a section. Creating a whole new record type sort of limit the other users from different profiles use the same accounts and see their highlights.

I believe this requirement is badly worded.
This was selected as the best answer
Carl Brundage (Dev)Carl Brundage (Dev)
I agree that creating a record type just to have a separate compact layout assignment may not be a best practice.  What happens when an account needs to be seen by both sets of users?  It certainly is the trick needed to pass this step and can be useful if there are other reasons for the record type.
Caleb SidelCaleb Sidel
@Samy - Yes the Record Type lets you pass, but having 2 Record Types does nothing to solve the requirement that one user see Accounts one way and another user see Accounts another way. The Compact Layout is assined to the Record Type regardless of profile so even if J has Record Type A and P has Record Type B if J is looking at an Account that P created - J will see it just like A does in terms of the Compact Layout (the page layout, sure that's by Record Type AND Profile)...I'm just talking about the Compact Layout.
Abhishek-tandonAbhishek-tandon
It still not working for me, tried below steps, not sure what is wrong here
Created
    1 Record Type Sales and assigned to Custom sales Profile where Sales
    
Create 2 Compact Layout
    1) Default Compact Layout: In which we have Account Name,Type,Phone,Parent Account and marked this as Primary Compact Layout
    2) Sales Compact Layout: In which we have Account Name,Employees,Phone,Rating and assigned it to Sales record type on Account
    
Changed the record type of one of the account record and validate the result for Sale user John it showing correctly

Bu still geeting error "Challenge Not yet complete... here's what's wrong: 
The custom set of fields that are highlighted on account records must be assigned to the required profile."
Carl Brundage (Dev)Carl Brundage (Dev)
Try a second record type for the other profile.
Abhishek-tandonAbhishek-tandon

It Worked @Carl , Thanks, But creating Record types should not be a good solution

sagar attuluri 4sagar attuluri 4
HI,
 I am getting error,
Challenge Not yet complete... here's what's wrong: 
The custom set of fields that are highlighted on account records must be assigned to the required profile.
 
Faiza Naz 10Faiza Naz 10
Hi,
Please check complete solution for this superbadge on below blog.
http://faizanaz90.blogspot.com/2017/09/salesforce-trailhead-lightning.html
Bhuvanesh Purohit 9Bhuvanesh Purohit 9
Hi All  : I actually configured as below, but somehow the primary compact layout is still driving the layouts for profile ( I have referred corrct record type at profile level). See below. Any suggestions ?

User-added image
Bhuvanesh Purohit 9Bhuvanesh Purohit 9
Basically I am still seeing the "Highlights panel" as per system default in primary compact layout and because we have 2 record types, I cant select either one of those as "Primary" . Still figuring out where is the missing link.
Bhuvanesh Purohit 9Bhuvanesh Purohit 9
ok. I resolved it finally after re-configuring & testing multiple times. The issue was altogether a simple thing. Had chose "Account Recpord Type" instead of "Type" field in one of the compact layouts. Sometimes , problems can be simplest, but just doesnt click.
Chris DuarteChris Duarte
@carl @samy what would you recommend we have you do instead of record types?
Carl Brundage (Dev)Carl Brundage (Dev)
If this were a customer, I would start by drilling down into the requirement more.  I would try to find out if there could be different fields that one group needs to see vs the other and control them with FLS in the Compact Layout.

If we could not get this to separate fields, I would try to encourage the client to only have the common ones in the compact layout.  Then use separate page layouts by profile to put the other fields on the account.  

If the client had to have separate fields in the header based on the user, I would create a lightning component.  Then use field sets to define what fields one user population wants versus the other.

The record type approach would only be used if there was another reason for the record type and the designations did not overlap.  For example, business account and person accounts.

Creating a user specific record type will run into problems when accounts are shared.  While Paloma works with top accounts, others will too.  However, the other users will not be able to see their fields as the account can only have one record type.
Chris DuarteChris Duarte
Thanks, @carl. In this case, we probably don't want them making a lightning component. We want to get them using the compact layout feature in Lightning Experience. We originally had them just make one compact layout, but wanted to add some more complexity. This is how the whole multiple layouts / record types thing came up.

If we wanted to add complexity to using compact layouts (but not involving code), what do you think would be a good scenario? 
Carl Brundage (Dev)Carl Brundage (Dev)
I would stick with one compact layout.  For added complexity, I would have users create a separate lighting page for the sales team and Paloma.  This would require assigning the layout by App+Record Type + Profile, which leverages the Lightning Experience functionality.  Paloma could need a report chart of avg days to resolve cases or related list that highlights cases in her role woking with strategic accounts.
Chris DuarteChris Duarte
These are great ideas, @Carl. Thanks for your feedback. *CHRIS DUARTE* Editor-in-chief, Trailhead | Salesforce
FonsFons
@ChrisDuarte Here's a recent idea that would be a better solution if it was live.  - "Allow Compact Layouts by Profiles"  https://success.salesforce.com/ideaView?id=0873A0000003UMhQAM

I agree with Carl and sticking to one compact layout.  

I cringe at needing to create another record type if the reason is to have different sets of users see a specific Compact Layout.  It's teaching Trailblazers this is an acceptable use case for new record types, and they may not understand the downstream implications (reporting, maintaining record types, picklist values based on record types, data cleanliness) plus adding workflows to convert a Record Type based on a value.    

If the theme here is on a Lightning Experience Rollout, an equaling challenging exercise would be to have users explore implications of maintaining/converting Classic and Lightning pages: new component visibility filters; adding quick actions so that they appear in Classic (from Quick Actions) and Lightning (from Mobile & Lightning Actions) since you have to do this twice and it’s not intuitive. 
MichaelFDenMichaelFDen
I used two compact layouts, one for John and one for Paloma.  It would not pass the test until I made the primary compact layout the same as John's compact layout.  The statement:

"Most Salesforce users at Lusso Scarpe work with account records on a regular basis. Using feedback from John and other sales team stakeholders, you’ve determined that the most important account details for sales reps are . . " 

Maybe implies that the Primary compact layout must be the same as John's compact layout, because that is what most users in the org use daily.  

compact layout assignment
JPSeaburyJPSeabury

I think you can meet the objectives of getting admins comfortable with the Highlights Panel and Compact Layout feature with some simple word smithing of the business use case. Make it clear that there are two types of accounts: Standard Accounts (managed by John's team) and Strategic Accounts (top tier accounts, managed by Paloma). Accounts might start as a "Standard Account", but once they reach a certain size, they are promoted (and their record type changed) to a Strategic Account.

The two "superusers" in our trial know that their peers need different information, and so the content of the Highlights Panel should reflect the most useful data for each team.

If you word it this way, you won't get custom highlight panels based on profile (or individual user), you'll get them based on record type. This probably more closely ressembles how record types are used, and should be familiar territory to Salesforce Classic admins. 

Filip Poverud 4Filip Poverud 4
So the objective here is not to use the Highlight panel but a Compact Layout ?

Will this be the case in the certification exam as well, when they ask you where to add fields to the highlight panel we should answer Compact Layout instead of Page Layout ?

Thank you for clearing this up.
Charissa JelliffCharissa Jelliff
I'm so glad I found this post, because I thought I was just missing something. The "correct" solution isn't really correct at all. I feel the correct solution to this part of the challenge should be to create different layouts and edit the highlights panel. Creating separate record types would actually create confusion in this case - in my opinion. 
Bob HatcherBob Hatcher
"Rating of how easy it is to do business with this account" means "Rating" not "Upsell Opportunity" - this tripped me up since I had the wrong field in my compact layout.
Mike.KatulkaMike.Katulka
I too am very thankful to find this post.

The solution required to create Record Types makes absolutely no sense. Account "Acme Corp" would need to be serviced by different team members.  To use recordtype means the Compact Layout would look different based on the ACCOUNT not based on profile. All users would see the same fields on Acme Corp regardless of their profile. 

This suggests that Paloma would service accounts 1-x, and need to see certain fields.

Other users would service "different" accounts? Sorry but this was a big detour, goes against core concepts of the platform. 

1. The tip at the bottom of this page is worded poorly too. All references of "user point of view" needs to be removed.  It should say "Here is how you display different fields in the highlights panel for different Account Record Types". And leave it at that.
https://trailhead.salesforce.com/modules/lex_customization/units/lex_customization_compact_layouts

2. The superbadge should simplify and remove the complexity it is checking for.  Otherwise it needs to look for a different solution, one that ends up being very custom, and nothing to do with Compact Layouts.  It should use the new conditional component rendering based on profile.  

3. Another option is to prioritize this idea, roll it out, update the superbadge to check for the usage of this: https://success.salesforce.com/ideaView?id=0873A000000CMajQAG
Carl johnson 18Carl johnson 18
Check this amazing article of latest Sims 4 vampire cheats (https://www.gtacheatcode.com/2020/01/sims-4-vampire-cheats.html)
Anthony SchneiderAnthony Schneider
Thank you for the solution.
Download Instagram Photos (https://www.onlineresizeimage.com/download-instagram-photos/)
Download Instagram Video (https://www.onlineresizeimage.com/download-instagram-video/)