Apex Code Development You need to sign in to do that
Don't have an account?
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.
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.
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
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.
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."
It Worked @Carl , Thanks, But creating Record types should not be a good solution
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.
Please check complete solution for this superbadge on below blog.
http://faizanaz90.blogspot.com/2017/09/salesforce-trailhead-lightning.html
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.
If we wanted to add complexity to using compact layouts (but not involving code), what do you think would be a good scenario?
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.
"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.
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.
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.
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
Download Instagram Photos (https://www.onlineresizeimage.com/download-instagram-photos/)
Download Instagram Video (https://www.onlineresizeimage.com/download-instagram-video/)
I have created two Record Types on the Account Object and created two Compact Layouts and assigned each to the correct one and am still getting the "The custom set of fields that are highlighted on account records must be assigned to the correct profile and include the required fields." error message. HELP!
I even changed the Primary Compact Layout to the Custom Sales Profile Compact Layout and am still getting the error message. UGH!!!
Beleive me all these Pinoy TV shows are the soul of all Ofw Pinoy TV lovers. pinoy tv shows (https://pinoynetworktambayan.com/)
Pinoy Tv Online
But this does not make sense. This will not fly as a solution in practice. The highlights display correctly for Paloma for newly created Accounts, but not for existing. And the Accounts Paloma creates appear in John's page with Highlights for Paloma's compact layout. I think the challenge should be based more on the real world use cases.
https://help.salesforce.com/articleView?id=sf.customize_recordtype.htm&type=5