Skip to main content

#Sales Cloud토론 중인 항목 104개

I actually successfully did this with a record triggered flow from this article (https://help.salesforce.com/s/articleView?id=000395389&type=1), but this only populates the field at the account (# of contacts) when a contact record is added or deleted.

 

Is there a similar flow that I could add or build that would allow me to run this as a 'one time event'?  I messed around for a bit but couldn't figure it out.

답변 15개
  1. 2023년 8월 14일 오후 10:21

    @Ryan Walsh Another quick way to get the field populated for the Accounts would be to run a report of "Contacts and Accounts", filter the report for All Accounts, <your count field> = "blank", group Rows by Account ID, and toggle "Detail Rows" off on the bottom. Once you save and run the report, export the results as a "formatted report" and you will have the list of Account Ids and their respective counts of Contacts, which you can then re-format the sheet with the appropriate headers and use Dataloader.Io to update. 

Akhilesh Prajapati 님이 #Salesforce Admin에 질문했습니다

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 

답변 2개
  1. 10월 30일 오전 10:16

    Hi @Forent Thomas

    , 

    So the scheduled mail, how did you implemented for every day to be sent, as this can't be done as manual.

Hi everyone,

I’d like to understand whether Zoom Phone, RingCentral, and Agentforce (including Prompt Builder) can be integrated with or used within Salesforce Experience Cloud.

Specifically, I’m looking for information on the following:

  1. Zoom Phone: Can Zoom Phone be integrated with Experience Cloud for making and receiving calls? Are features such as click-to-call, call logging, and CTI supported for community users?
  2. RingCentral: Does RingCentral support integration with Experience Cloud? If so, what calling and telephony features are available to external or community users?
  3. Agentforce and Prompt Builder: Can Agentforce agents be deployed within an Experience Cloud site? Can prompts created using Prompt Builder be used by community users, and what are the available options and limitations?
  4. Licensing requirements: What Salesforce licenses, Experience Cloud licenses, Agentforce licenses, or third-party subscriptions are required to enable these features?
  5. Configuration and limitations: Are there any additional setup requirements, supported integration approaches, permissions, or known limitations to consider?

If anyone has implemented these solutions, I’d appreciate details about the recommended approach, licensing costs or requirements, and any practical experience or documentation you can share.

Thanks in advance! 

 

#Salesforce Developer #Salesforce Admin #Agentforce #Salesforce #TrailblazerCommunity #Sales Cloud    #Experience Cloud #Digital Experience #Lightning Experience

답변 2개
  1. 10월 30일 오전 1:31

    Hi @Ali Azam

     

     

    Here’s what I’d go with based on what I’ve seen or read so far:

    Zoom Phone and RingCentral: both connectors are built on Open CTI, which is designed for internal users in Lightning apps (the softphone in the utility bar). As far as I know, Experience Cloud sites don’t support the Open CTI softphone. So for community users you’re usually looking at: 

    • Simple tel: click-to-call links.
    • The vendor’s web or embed SDK wrapped in an LWC, with call logging done through Apex or the vendor’s API. 

       Either way, confirm with Zoom and RingCentral, since their packages are licensed for internal users.

     

    Agentforce: yes, a service agent can be deployed to an Experience Cloud site through Messaging for In-App and Web (Embedded Service). This is the cleanest supported path. 

      

    Prompt Builder: I wouldn’t expose it to external users directly. Invoke the prompt template from Flow or Apex behind an LWC or an agent action, and control what data goes into the prompt. Watch sharing, FLS and PII for external users. 

      

    Licensing: you’ll need Experience Cloud licenses (Customer or Partner Community), Agentforce consumption (Flex Credits or per-conversation pricing), Data Cloud provisioned for Agentforce, and separate Zoom or RingCentral subscriptions. I suggest connecting with your AE to confirm current pricing, as it changes often.

Leah Nordlund 님이 #Sales And Marketing에 질문했습니다
Currently we do not have Jitterbit up and running and need to do manual customer integrations. Cannot locate our documentation.
답변 1개
  1. 10월 29일 오후 10:12

    To perform a manual customer integration from Salesforce to Dynamics GP without Jitterbit, you will need to export the customer data out of Salesforce into a structured format (such as a CSV file via reports, Data Loader, or data export) and then import it into Dynamics GP using one of its native loading tools. The most efficient native approach in Dynamics GP is using Integration Manager if you have it licensed and configured, or utilizing the Mass Modify / SmartConnect features if available in your environment. Alternatively, for smaller batches of records, you can use the Integration Manager Express tool or the built-in Data Import utility within Dynamics GP to map your Salesforce CSV columns directly to the Customer Maintenance tables and batch-import the records.

Hi Salesforce Community,

 

We have a requirement to capture a Site Visit confirmation (Picklist field - Yes/No) from the approver before they approve a Salesforce Opportunity. We are currently using a

Classic Approval Process

and want to provide this input directly on the Approval Request screen, without requiring users to navigate back to the Opportunity record. 

 

We have explored the standard Salesforce configuration and encountered the following limitations: 

 

  1. Conditional Visibility: Lightning App Builder does not appear to support component visibility rules on the standard Approval Request Lightning Record Page. 

     

  2. LWC/Flow Placement: We could not find a supported way to add an LWC or Screen Flow exclusively to the Approval Request screen with conditional visibility based on the related Opportunity. We would also like to understand  

     

  3. Editable Fields: Fields displayed on the standard Approval Request screen appear to be read-only. Is there a supported way to make a custom picklist editable directly on this screen? 

     

  4. Approve Button Customization: Is it possible to customize or override the standard Approve button to capture additional input before processing the approval? 

     

  5. Custom Actions or Buttons: The Approval Request object does not appear to expose the usual custom button/action creation options available on standard Salesforce objects.

Our expected behavior:

  • Display the Site Visit (Yes/No) field only when the related Opportunity meets all these conditions:
    • Stage = Qualified
    • Record Type = Booking
    • Status = Pending Approval
  • Allow the approver to select Yes/No and click Approve on the same screen.
  • Allow approval only when the answer is Yes; block approval when the answer is No or blank.
  • Preserve the existing Classic Approval Process and its Manager → Branch Manager approval sequence.
  • Provide a user-friendly experience on both desktop and mobile.

Questions:

  1. Is there a supported Salesforce configuration or customization approach to achieve this directly on the standard Approval Request screen?
  2. Can an LWC, Screen Flow, or custom action be embedded in the Approval Request page and interact with the existing approval work item?
  3. If this is not supported on the standard page, what is the recommended approach for integrating custom input with a Classic Approval Process without forcing users to navigate between screens?
  4. Has anyone implemented a similar solution using LWC, Apex, or another supported Salesforce extension?

We are specifically looking for a solution that modifies the existing standard Approval Request screen

, rather than asking users to open a separate custom approval page or navigate back and forth between the Opportunity and approval screens. 

 

Any official documentation, technical guidance, or working implementation examples would be greatly appreciated.

 

Hi Salesforce Community, We have a requirement to capture a Site Visit confirmation (Picklist field - Yes/No) from the approver before they approve a Salesforce Opportunity.image.pngimage.png

 

 

 

 

#Sales Cloud  #Approval Rules Setup  #Approval Actions  #Approval Record  #Salesforce Developer  #Salesforce Admin

Hi all! I think I can't get around this but I'm wondering if anyone has any ideas. I have two lines of business (line a and line b) and line b wants to see some information from line a. Previously this has not been needed or possible. 

 

I have managed (using a looking field on the opportunity and a sharing rule) to make that happen. The problem is that if line b runs an account report (for example) they get line a info and we don't want that to happen. If I remove the sharing rule that makes this whole thing work - what I created falls apart. 

 

I'm thinking the only way is do something thing that would require a LOT of work and probably involve bringing in a developer - one or more of the following 

- custom dl account reference object 

- screen flow search 

- custom LWC 

anyone have any other thoughts/ideas? 

Thank you in advance as always for any help!  :) 

 

#Salesforce Admin  #Salesforce  #Sales Cloud  #Automation

답변 5개
  1. 10월 28일 오전 9:50

    Hi @Bill Hare

    I think the issue is related to Salesforce's record-level sharing model. A sharing rule that grants Line B access to Line A's Account records can also make those records available in Account reports.

    Before building a custom LWC or Screen Flow, I would consider these options:

    1. Field-Level Security: If Line B should see the Account records but only specific information, use field-level security to hide sensitive fields. However, this won't prevent Line B from seeing the Account records themselves in reports.
    2. Restriction Rules: Check whether restriction rules are supported for the object and use case. They can filter records users can access, but they don't provide field-level access control and aren't available for every standard object.
    3. Custom Object: If Line B only needs a small subset of Line A's information, create a custom object containing only the information that Line B is allowed to access. Share those records with Line B without granting broad access to the original Account records.
    4. Custom UI: If Line B only needs to search for and view selected information, a custom LWC or Screen Flow could provide a controlled interface. Make sure the underlying Apex enforces the required access restrictions; hiding records in the UI alone is not a security boundary.

    My recommendation would be to clarify whether Line B needs access to the entire Account record or only a few fields. If it is only a few fields, a separate custom object or a carefully designed sharing model may be cleaner than sharing the original Accounts.

    Salesforce references:

    I hope this helps! If you find this answer helpful, please select it as the Best Answer. 

     

    Thanks, 

    Deepak Sachdeva 

    Nubys Technology Pvt. Ltd.

Hello Trailblazer Community! 👋

I have 10+ years of experience in Software QA, ETL Testing, Data Quality, SQL, Test Automation, Functional Testing, and UAT.

I am transitioning into the Salesforce ecosystem with the goal of becoming a Salesforce Functional Consultant, focusing on Sales Cloud, Salesforce CPQ, Revenue Cloud, and Agentforce.

I am currently building hands-on Salesforce portfolio projects to strengthen my understanding of business requirements analysis, business process mapping, user stories and acceptance criteria, product configuration and pricing, Quote-to-Cash processes, functional testing, and UAT.

I am particularly interested in understanding how Salesforce solutions are designed and implemented to solve real-world business problems.

I would love to connect with Salesforce Functional Consultants, Business Analysts, CPQ and Revenue Cloud professionals, Agentforce specialists, and Salesforce implementation partners.

I welcome opportunities to learn from experienced professionals, exchange knowledge, build meaningful connections, and explore relevant career opportunities in India.

If you have any advice for someone transitioning into Salesforce Functional Consulting, I would be grateful to hear your suggestions.

Looking forward to connecting with fellow Trailblazers!

Thank you!

 

#Sales Cloud  #Salesforce Revenue Cloud  #Salesforce CPQ & Billing  #Agentforce  #Salesforce Admin

Nizar Am 님이 #Salesforce Developer에 질문했습니다

Hi everyone,

I'm really stuck here with a strange issue I'm facing. When a user creates a Case and adds an Invoice Line through a Screen Flow.

The Case is created successfully, but the Flow fails when creating the related CaseInvoiceLine__c record, with the error INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY.

What’s strange is that the user has access to both the Invoice and the Invoice Line. I also tested using the same user account with a different account, as well as with a different invoice line from the samme account, and the Case was created successfully. The error only occurs with this specific Account.

Has anyone encountered something similar or have any ideas about what could cause this? Any help would be greatly appreciated!

Thanks in advance! 

 

#Salesforce Developer  #Salesforce Admin  #Sales Cloud

답변 4개
  1. 10월 28일 오전 8:48

    Hi Nizar, just checking in before the community goes read-only on Oct 30. Did this solve it? If it did, marking it as the best answer would help others who find this thread later. Happy to dig in further if something's still off.

Abby M 님이 #Trailhead에 질문했습니다

Is there a free version to do this on the Contact object? 

 

If there's a first name/last name match via LinkedIn?  

 

#Trailhead  #Salesforce Developer  #Salesforce Admin  #Salesforce  #Data Management  #Sales Cloud

답변 2개
  1. 10월 28일 오전 8:47

    Hi, checking in before the community becomes read-only on Oct 30. Did the LinkedIn approach work for you? If it did, selecting it as the best answer would help future readers. Happy to help further if you hit any snags.

I am trying to extract an user email to an custom email field ( OppUser__Email)under opportunity from user object, based on an given name in the opportunity.

 

For example:  I have 50 users using salesforce,  and they all have full name & email set up etc.. and I have created a custom user name pickup list field(OppUser__Name) in the opportunity object, and it can be any users depending on the opportunity record, so I want to extract the email address based on the  OppUser__Name.  Thanks 

답변 3개
  1. 2024년 4월 17일 오후 3:08

    Thanks Guys,      Owner.Email isn't working as  OppUser_Name  is not the record owner,  all  names in the OppUser_Name field are the salesforce users, and their email address is in the user details,  Just think if I can create a new field  OppUser__Email ookup the OppUser_Name field in opportunity, and find the name field in the user then extract the user's email address  from salesforce user details to opportunity field OppUser__Email