Skip to main content

#Salesforce Developer439 debatiendo

Agents have FLS for most fields on opportunity and we have something called SA1 records. Those are the records owned by 'System Admin 1' user. Agents can access those records from a related list. But we wanna restrict them to search for Opportunities with just email or phone. They should not be able to find say opportunities in a particular state or address from global search.

#Salesforce Developer #Salesforce Admin #Systems Administrator #Administrator #Advanced-Administrator #SF Developer #Platform Developer #SF Developers #Application Architecture #Ladies Be Architect
2 respuestas
  1. 10 oct, 12:25

    Global search looks through all the fields a user can see, so there is no setting to limit it to just email and phone. If agents do not need to see state or address at all, remove read access to those fields in field-level security and they will stop appearing in search. If agents need to see those fields on the record but you only want search by email or phone, you would need a custom search screen instead of global search. A simple option is a list view with filters on email and phone that agents use instead of the top search bar.

0/9000

Hello Salesforce Community,

I need help recovering my original Salesforce Developer Edition org enabled with Agentforce and Data Cloud.

I received an email from Salesforce on October 11, 2026, stating that my org would be deleted if I did not log in by October 25, 2026. I am now unable to access it and see the message “Your Salesforce trial has ended.”

My org ID is 00DdL00000xzS7E.

I have an important Event Management project in this org, including custom objects, fields, Flows, Apex classes, triggers, and Experience Cloud customizations.

I originally created this as a free Developer Edition org. Could someone help me verify its current status and advise whether any recovery option is available?

I would really appreciate your guidance. Thank you! 

 

#Salesforce Developer

3 respuestas
0/9000

"DevOps Center Setup" this quest in my org I am unable find my DevOps Center Admin in permission sets, how to get this option. After enabling Dev hub and Life Center packages it still not work for me. Anyone please help in this matter because I think my Org not performing correctly. 

 

#Trailhead Challenges  #Salesforce Developer #Trailhead #Salesforce Admin #TrailblazerCommunity #Trailhead Support

4 respuestas
  1. 27 oct, 14:57

    Hi @Eric Burté

     

     

    Because of some mistakes I couldn't find my answer, thank you Eric.  

     

    Thanks and Regards 

     

    Palash

0/9000

Context

We recently experienced an Email-to-Case outage where a mailbox forwarding configuration was updated for a Sandbox request, but the forwarding rule was actually tied to the active Production Email-to-Case process. This unintentionally disrupted Production email routing and prevented incoming emails from being automatically converted into Salesforce Cases until the routing configuration was restored.

As part of our ongoing Email-to-Case enhancement and Hyperforce migration efforts, we would like to understand what contingency options are available to ensure business continuity if email routing or forwarding configurations fail in the future.

Ask

Looking for recommendations and best practices from the community on:

  • What backup or failover mechanisms can be implemented for Email-to-Case?
  • How can we ensure inbound emails continue to flow into Salesforce if mailbox forwarding fails or is misconfigured?
  • Are there monitoring, alerting, or health-check approaches that can proactively identify Email-to-Case routing issues before business users are impacted?
  • Has anyone implemented secondary routing addresses, backup mailboxes, middleware, or other resilient architectures for Email-to-Case?
  • Any lessons learned or best practices for Hyperforce migrations and Email-to-Case resilience?

We would appreciate insights from teams that have implemented a robust Email-to-Case recovery or failover strategy to minimize service disruption. 

 

#Salesforce Admin  #Systems Administrator  #Salesforce Developer  #Salesforce_developer  #Email-to-case  #Trailhead    #Sales Cloud  #Service Cloud 

0/9000

Getting error while validating challenge. I have completed all the steps according to the module. Any solution for this ?  

 

Get Started with Prompt Builder

 

 

 

#Trailhead Challenges  #Salesforce Developer  #Trailhead  #Agentforce  #TrailblazerCommunity  #Certifications

3 respuestas
  1. 27 oct, 8:26

    Salesforce Support has confirmed that this is a known issue. 

     

    Workaround to complete the challenge

    : Creating a new Org again from scratch and repeating the steps fixed the issue.  

     

    To create a new Org using the button "

    Create Playground" on the unit, you should create a normal Playground from Profile > Hands-On Orgs

    section. 

    This will allow you to

    Disconnect existing Einstein AI Playground

    from your Trailhead profile. 

    Once the exisiting Playground is disconnected, you will see "

    Create Playground

    " button on the unit once again, you can use the same to initiate the creation of new Einstein AI Playground and repeat the steps. 

    This has worked for me & I was able to complete the badge. 

     

    cc:

    @Mahesh A

     

    #Trailhead Challenges #Agentforce #Trailhead #Salesforce Developer #Salesforce Admin

0/9000

For the Get Started with Prompt Builder, I created the Field Generation Prompt Template 'Quick Summary' for the first time in my playground and misspelled it as 'Quick summary' (with a small 's'). API name also took small 's' in summary automatically. I have completed the exercise successfully but when Salesforce tries to verify and give me points, it fails to find the  Field Generation Prompt Template named Quick Summary. I am unable to mark this complete and move on to the Prompt Builder Templates Superbadge Unit. I tried to create a new version of the prompt template but it gives the same error again. How do I resolve this?

28 respuestas
0/9000

Hi Trailblazers,

In our Salesforce application, we have an LWC that displays records and provides configurable action buttons. Based on the selected action, we need to invoke a Screen Flow, another LWC, or an Aura component.

Currently, we use Lightning Message Service (LMS) to communicate with a separate helper component that is placed on the Lightning record page. The helper component receives the message and handles the corresponding action.

We would like to simplify this architecture by removing both LMS and the helper component.

My questions are:

  1. Can we launch a Screen Flow directly from our existing LWC using lightning-flow, without LMS or a helper component?
  2. Can we invoke or display another LWC directly from our existing LWC based on a configurable action?
  3. Can we invoke an Aura component directly from an LWC without using a helper component?
  4. Is there a recommended Salesforce architecture to support all three types of actions dynamically from a single LWC action button?

Our requirement is to support configurable actions rather than hardcoding each target component.

I understand that the approach may differ for Flow, LWC, and Aura components. I would appreciate any recommendations, limitations, or best practices for achieving this without LMS and a separately placed helper component.

Thanks in advance! 

 

#Salesforce Developer

0/9000

I'm trying to deploy an Enhanced LWR Experience Cloud site from my source org to a target org using VS Code and Salesforce CLI. I'm facing an issue retrieving the DigitalExperienceBundle metadata.

Environment

  • Site Name: Employee Portal1
  • Framework: Lightning Web Runtime (LWR)
  • Site Type: Enhanced LWR
  • Metadata API version: 67.0
  • Tool: VS Code / Salesforce CLI

Problem

In Experience Builder, the site is displayed as Employee Portal1, with Lightning Web Runtime and the Enhanced badge.

In my local Salesforce project, I have the following metadata:

  • DigitalExperienceConfig/Employee_Portal12.digitalExperienceConfig-meta.xml
  • ExperienceBundle/Employee_Portal1
  • ExperienceBundle/Employee_Portal12
  • Network metadata for Employee Portal and Employee Portal1
  • CustomSite metadata for Employee_Portal and Employee_Portal11

However, the DigitalExperienceBundle folder is empty.

I have enabled Enable ExperienceBundle Metadata API in Setup → Digital Experiences → Settings.

When I run the following command:

sf project retrieve start --metadata "DigitalExperienceBundle:Employee_Portal12" --target-org <SOURCE_ORG_ALIAS>

I receive this warning:

Nothing retrieved

Entity of type 'DigitalExperienceBundle'

named 'Employee_Portal12' cannot be found

My DigitalExperienceConfig file contains this reference:

<space>site/Employee_Portal12</space>

During deployment, I also receive this error:

In field: space - no DigitalExperienceBundle named site/Employee_Portal12 found

Other deployment errors indicate missing Network references, an audience without criteria, and an unsupported emailDomainSubstitutionEnabled property in API version 67.0.

What I've tried

  1. Enabled ExperienceBundle Metadata API.
  2. Tried retrieving DigitalExperienceBundle using Salesforce CLI.
  3. Checked the local metadata folders in VS Code.
  4. Confirmed that the site is an Enhanced LWR site in Experience Builder.

Questions

  1. Why is Salesforce unable to find the DigitalExperienceBundle when the site exists in Experience Builder?
  2. Could the site have been created or migrated using the older ExperienceBundle metadata type?
  3. Is there a recommended way to retrieve or migrate an existing site from ExperienceBundle to DigitalExperienceBundle?
  4. Should I rename the existing target site and update its Custom URLs before deployment, as described in Salesforce's guidance for migrating non-enhanced LWR sites?
  5. How can I correctly deploy the LWR site with its DigitalExperienceConfig, Network, CustomSite, navigation menus, and branding metadata?

Any guidance or a working deployment example would be greatly appreciated. Thank you! 

 

#Salesforce Developer  #Trailhead Challenges  #Trailhead

5 respuestas
  1. Ayer, 5:24

    @HARIPRASAD Km

    • If your local Salesforce CLI or sfdx-project.json file defaults to an API version lower than the org's current release, the CLI fails to map the enhanced LWR architecture correctly.
    • The string you pass to the CLI or put in the <members> tag of your manifest must be the unique API Name (DeveloperName) of the site workspace, which is frequently different from the user-facing site name.
    • Retrieving a DigitalExperienceBundle strictly by name directly from the CLI command can occasionally miss mappings if local configuration tracking gets out of sync. A structured package.xml manifest forces the Metadata API to evaluate the package constraints directly.
0/9000

I had a base 1GP managed package and 1 unmanaged packages. Recently i converted the based package to 2GP and wanted to convert the 1GP unmanaged packages to 2GP. 

I have looked for a way to do this and Unlocked packages(no namespace) seems to be the best way to do it. I have tried converting the same metadata of unmanaged package to Unlocked Package and installed in a test org, the unmanaged package fields do list under the Unlocked Package, But also under the Unmanaged package. I tried deleting the unmanaged package but it also removes the components under it. 

Need a way so i don't have to keep the Unmanaged package in the org after i have the Unlocked package. How you all are handling this scenario? 

 

#Second Generation Packages  #Generation Managed Package  #Salesforce Developer  #Solution Architects

1 respuesta
  1. Ayer, 6:53

    Hello @Abhishek Sinha

     

    Package conversion and migration to 2GP only work for managed 1GP packages. Unmanaged packages can't be converted. For those, you rebuild the package from its source. 

     

    If it's an unmanaged package:

    1. Retrieve the package's metadata into a Salesforce DX project:

      sf project retrieve start --package-name "<Package Name>" --target-org <org>

      Then convert it to source format if needed: sf project convert mdapi.

    2. Create a new package from that source. Use an unlocked package for internal/org use, or a managed 2GP package if you're an ISV distributing on AppExchange:

      sf package create --name "<Name>" --package-type Unlocked --path force-app

      sf package version create --package "<Name>" --installation-key-bypass --wait 20

    3. In existing orgs, the unmanaged components aren't linked to any package. Install the new package and test it in a sandbox first. Unlocked packages can take ownership of existing unpackaged metadata (see "Migrate Existing Metadata to Unlocked Packages" in the docs).

     

    If it's a managed 1GP package, Salesforce supports conversion and migration in three phases:

    1. Plan and test: keep releasing with 1GP. Convert and migrate only in scratch orgs or sandboxes. Get all subscribers onto the same 1GP version.

    2. Transition: convert your latest major.minor released version, promote it to released, then migrate subscribers with push upgrades (one time per subscriber). New features are still built in 1GP, then converted and push-upgraded.

    3. Fully on 2GP: confirm the move in your packaging org's Setup. After that, you can no longer create new major/minor 1GP versions (only patches for earlier versions).

     

    The subscriber's installed 1GP version must match the major.minor.patch version of the converted 2GP version you migrate them to. Migration doesn't change your metadata or subscriber data. 

     

     

0/9000

Good afternoon everyone, hope you are doing well. 

 

I would like to ask a few questions regarding sandboxes in MARKETING CLOUD NEXT, which came up as I started on a new project. To give you some general context, this client basically wants to do all the development in the sandbox, and once everything is validated and tested, deploy it to production—which is totally fine.

 

 

However, here are my questions: 

 

1 - Regarding WhatsApp: Can I perform the setup configuration, warming, and testing all within the sandbox? My concern is whether I will need to replicate this entire process in production later on. If there is an ideal scenario or best practice, I would like to understand how to proceed with this step. 

 

2 - Regarding Email: Similar to the WhatsApp situation, my main question is about the domain/subdomain in the sandbox. When doing all this setup, do I need to perform the IP/domain warming normally? Is it necessary to create a domain/subdomain to work in the sandbox as well, and then repeat the same step for production? Or is the process different for a sandbox? 

 

In short, these are my main questions, but just to reiterate: this client wants everything to be developed and tested in the sandbox, and we will only deploy to production once everything is validated.

Because of this, I have these questions so I can understand the best way to move forward. 

 

Thank you. 

 

#Trailhead  #Salesforce Developer  #Salesforce Admin  #Salesforce  #TrailblazerCommunity  #Marketing Cloud

2 respuestas
  1. Ayer, 19:29

    Good afternoon, @dhanush gunda how are you?

    The answers were great and have really given me clarity to move forward with the planning. However, there are just a few points I would like to confirm: 

     

    1 - Email: regarding the test subdomain, do you mean we should create one specifically for testing in the sandbox? Or would we not even need to create one in this case? I would like to understand this point better, since it's already clear that we won't be doing the warm-up in the sandbox. 

     

    2 - WhatsApp: does the "Meta Test Sup" you mentioned mean requesting a test number when configuring the number? I believe I will actually need one to test in the sandbox, and then later register the company's single official number in production. 

     

    Thank you!

0/9000