All components are built in a scratch org. When I tried to pull the components from scratch org to repo, I received the error: Entity of type 'Layout' named 'CML_Case__c-Case Layout' cannot be found
Entity of type 'Layout' named 'CML_Case__c-CML Case Page Layout Type 3' cannot be found.
Please let me know how I can resolve this and move all my components to the repo successfully.
Try to use CLI:
sf project retrieve start -m "Layout:ObjectName-Layout Name"
Hello all, I am trying to retrieve a layout in FSL through package.xml from the Work Order object but the layout cannot be found.
I tried retrieving sing this:
<types>
<members>WorkOrder-FSL Work Order Layout</members>
<name>Layout</name>
</types>
Does anyone know what is wrong with this? Thanks.
Screenshots:
Hi @Jaemy Malik,
Please check the below links.
https://developer.salesforce.com/forums/?id=9062I000000IZRfQAO
https://salesforce.stackexchange.com/questions/250268/retrieve-page-layouts-in-source-format
I hope this helps!
Thanks
Saurabh
TL;DR: In need of specific instructions to enable SMS-based login with SMS TOTP for Experience Cloud
Hello – I am seeking support from this community to implement a specific login option for Experience Cloud. Getting this solution implemented will benefit thousands of deserving families served by our client.
What we need to set up:
Users need to login to Experience Cloud via their mobile number (not an email address). For identity verification, users need to receive a TOTP (time-based, one-time password) texted code (via SMS, not a third party authentication app).
Though I have searched the Help documentation and Trailhead for hours trying to solve this on my own, I simply cannot find a clear set of instructions for what to do anywhere. Everything I do find takes me to instructions for a different option than what we are trying to implement.
Here are the pertinent details:
I have already consulted with Experience Cloud experts within my own organization; it just has not come up on any project before. SMS authentication is not my personal area of expertise either. I would greatly appreciate a set of clear instructions – where to go, what to enable or configure, ideally specific and making no assumptions that I’ve had previous experience with Mobile Identity or Salesforce Identity or any of those other products.
If you don’t have those details, but you have hints, or are willing to @mention someone you think may know how to do this, that would be great too!
When I get the details and confirm it’s working, I’ll gladly share any learnings for anyone who finds themselves in this situation in the future! Thank you for your support!
There is a whole side to this that is not documented anywhere and in a recent implementation of passwordless I went through it.
After completing all the settings that you might find online, you will find that there is no standard way to verify the mobile number for external users, so you will need to build something that allows the external user to verify their mobile (we built an LWC).
Also, if you are not using Self-Registration, there is a hidden field (not mentioned anywhere) called "Admin Trusted Mobile Number" which only gets checked off when the self registration is done and the user verifies their mobile number or when an Administator (User with a System Administrator profile) enters their mobile number in their user record.
So even when the users can edit their profile and through your LWC they can verify the mobile number, if an Administrator did not enter that information in the user record, the Standard Login Discovery will not allow the user to login.
I am trying to build something around that so that the process is not so painful for existing experience cloud users or non-self-registered users.
Will keep you posted on the findings.
Hi, I am received the password reset link but I forgot to reset the password and the link was expired in 24 hours. How to request for a new password link?
#Trailhead Challenges #Agentforce
Hello All,
Could you please help me with the following question:
We are using the email service TicketsFromEmail with the Apex class MailListen_IncidentCTHandler to automatically create incidents in Remedy from incoming emails.
Recently, the Apex class was updated in the Sandbox environment by adding the following line:
incident.Title__c = email1.Subject;
This change is intended to populate the Title field of the newly created incident using the subject line of the email that triggered its creation.
However, when I send emails with the template name in the subject line (e.g., EQNH New Hire - Test Test_06/23/2025) to create an incident using that template, the Title field in the incident includes the entire subject line, including the template name (e.g., "EQNH").
Could you please help me understand how I can update the Apex class—or specifically the newly added line
incident.Title__c = email1.Subject; —so that the template name (e.g. EQNH) is excluded from the Title field of the created incident?
Thank you in advance!
It appears that the Admin Advanced
trail is defunct! Let me know what would be the most helpful trail to pursue next as someone who is still a relative rookie. Thank you!
#Trailhead
No puedo ver nada...
El vie., 27 de junio de 2025 16:27, Salesforce Trailblazer Community <
trailblazercommunity-notif@salesforce.com> escribió:Hi All,
I'm working with
Second-Generation Packages (2GP) for the first time. I've successfully added a namespace (from another Dev org), created a managed 2GP, built a package version, and promoted it as a released version. I also have the installation link for the package.However, I'm facing an issue — I can't find the package details in the Salesforce Org where we typically view First-Generation Packages
under:
Setup → Package Manager → [Package Details]
I've followed the same steps expecting to see my
Second-Generation Package details, but it's not visible there. Could you please guide me on the correct location or steps to view Second-Generation Package details in the Org? I want to make sure I'm not missing something in the process.Appreciate your support!
#Second Generation Packages #Package Manager #Salesforce Developer #Salesforce Developers #Developer Forums
We've used ZuAnt (3rd party vendor) in the past but it doesn't update the existing Salesforce records and results in a lot of duplicates, plus we can't use it to record opportunities generated at the show not to mention it's been cut from the budget. Our developer isn't sure how best to build this using just Salesforce or Pardot. For Salesforce I was wondering if it's a junction object to connect different campaigns to different trade show activities. Or I feel like we could use Pardot in Kiosk mode but if they are already existing customers we will asking them for data we technically already should have. Anyone have a great system they want to share?
My advice having done a lot of trade shows is to use an Account Engagement native form in kiosk mode that redirects back to itself on submit (or to a landing page that says "success" and automatically reloads the form after a moment). This will not create duplicates in Account Engagement of the same email address, it will update the record with the most recent activity if there's duplicate emails, or if the person already existed in Salesforce it will synchronize there. But as you point out, it's possible you are collecting information you already had, but there's really no good way to do a lookup from a kiosk form to see if they are already in the system, unless you are having them shoot a QR code to a form that isn't a kiosk -- if their device happened to be cookied then you could not ask for fields you already had (or show them pre-filled out)
In either case, you can have prospects self-fill the form, or show staff can use the kiosk from business cards, or from a sheet of paper. From my years of experience in this area, I will also say that event wifi can be flaky so always make sure you have a backup entry method available. Plus you get all the advantages of completion actions the moment one is entered, so associate these records to a campaign for the show and then you get the attribution engine moving for opportunities that arise from the event (campaign attribution requires that your sales staff use opportunity contacts to work, so make sure that they do!), and use completion actions to send a thank you email, start a followup engagement studio, assign new records, etc. The only real hurdle here is prospect behavior at the trade show. It's a disruption of the rhythm of the conversation to ask them to fill out a form.
I am testing a flow that sends SMS messages to out customers. It is the same flow in our production org. It should send a SMS Text message when an appointment is scheduled, but nothing happens while testing in our sandbox. The flow is working in our production org, so I am not sure why it isn't working in the sandbox. Is it a different action for enhanced channels. We do have enhanced channel turned on in the sandbox but not in our production org. #Flow #Digital Engagement
