see attached screenshot for reference, in the page editor, it is showing correctly, but out of nowhere it randomly just stopped wrapping the text so the item description is cut off unless you click into it
Forum Ambassador
I found the solution for this Need to enable these 2 check boxes from system permissions on profile
1.View All Data
2.View Shield App Pages
I'm a Salesforce consultant. Every project I've worked on started the same way: a Figma or grey-box wireframe that the client signs off, then a build that surprises them, because a picture of a Lightning page is not a Lightning page. Hover cards, path chevrons, related lists, the way a quick action opens: none of it is in the mock-up, and the review meeting turns into "is this what Salesforce looks like?" instead of "is this the requirement?".
What I've been doing instead is building the page itself in the real Lightning Design System from the user story, in both the SLDS 1 and SLDS 2 looks, then clicking through it with the client and reading the acceptance criteria back off the page. It has changed our review meetings, but I'd like to know what others in this group use:
Do you prototype in the SLDS Figma kit, or straight in App Builder in a sandbox?
How do you show interaction (quick actions, screen flows, popups) without building it for real?
How do you handle the SLDS 2 transition when the client's org still shows the classic look?
Full disclosure: I built the tool I use for this (
sfproto.com, free to try, nothing connects to an org). That's not the point of the question, but I'd rather say so than not.I'm a pretty big fan of simply defining a beta app inside the production org and creating a lightning record or app page, preferably by copying the existing page as foundation. Add that record page as the Default page in the new beta app. Now make whatever changes you plan to make. If it's a big production change that will take a lot of work, place a rich text element describing what you're going to do in Mockup. If you're going to design a custom component, add a component very similar to what you plan to do, use it but add rich text above it explaining the difference. If you plan to add custom buttons, you can mock those up with a rich text element also or even other things more button like. Now you can show the page to whomever needs to give feedback.
I actually roll out new pages this way. I developed the fully functional page inside the beta app and tell people there's a better way if they want to give it a try by switching to the beta app and then when everything stable, we just change the the default page (org wide if applicable) over to the new page and it's done.
Another nice thing for users is to have a little rich tech somewhere down at the bottom or your production pages that actually list the revisions made to the page. You can include hints, too, since change is usually aimed at better effeiciency or process.
Prospect Rating is set to Required but Customize Record Pages challenge won't verify
Post:
To complete this Trailhead challenge successfully in the Lightning App Builder, you need to make sure she has first upgraded the page layout using Dynamic Forms
To resolve this, open your trailhead playground, navigate to setup, and type agentforce agents in the quick find box. Once you are on the list view of all active and inactive agents, click into the duplicate Sales Coach Agent records to inspect their details
Hi @Sri Lakshmi Dusanapudi Click on the hihlight panel component area (as shown below) and if the page needs an upgrade then button will show on the right side otherwise its already upgraded.
Thanks Keji,
I was able to resolve it reading through the link you sent.
Hi Salesforce Community,
I’m working in Lightning Experience and I have multiple Lightning Record Pages for the same object (using different Apps / Record Types / Profiles as needed).
I need to display the same field with a different label depending on which record page the user is viewing. Example:
I know the standard field label is global for the object, and if I change it, it changes everywhere.
My question:
What’s the recommended way to show a
custom label per page for the same field on different record pages?What I’ve tried / considered:
If anyone has best practice guidance (I would like try native salesforce option other than LWC), I’d really appreciate it.
Thanks
Hello @Trupti Labhasetwar
You can’t natively show different labels for the same field on different Lightning Record Pages for the same object. The field label is global and stays the same across layouts, apps, record types, and pages.
The only time different labels are possible is through translations based on user locale. If users have different languages set, you can translate the field label so each locale sees a different name, but this won’t work for different pages with the same language.
If you just need a different display label on another page, a common native workaround is to create a formula field that references the original field and give it the alternate label. You can place the original field on one page and the formula field on another. This works well but is read-only, so it’s not suitable if users must edit the value in both places.
I hope this helps
