#TrailblazerCommunity181 discutindo

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! 

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. 

I am currently encountering a similar challenge. I am building a custom Lightning Web Component (LWC) to replicate standard Salesforce List View functionality, which will allow users without administrative access to create and manage their own list views. I am utilizing Named Credentials to handle the creation and updating of these list views.

However, I am running into a few issues:

First, I am unable to retrieve only the fields that are eligible for List View creation. When I fetch the fields for the User object, the system returns every field on the object. I have realized that not all of these fields are actually available or supported for use inside a standard List View.

Second, when attempting to save the list view via the Metadata API, the standard SOQL field API names fail. When I fetch an existing list view to inspect it, the XML returns completely different internal API names, as shown in the snippet below: 

<ListView xmlns="

http://soap.sforce.com/2006/04/metadata

"> 

    <fullName>testing_list_view_2</fullName> 

    <columns>CORE.USERS.FAX</columns> 

    <columns>CORE.USERS.FIRST_NAME</columns> 

    <columns>FULL_NAME</columns> 

    <columns>DVC_Is_Manually_Cleared__c</columns> 

    <columns>CORE.USERS.LAST_LOGIN</columns> 

    <columns>CORE.USERS.LAST_NAME</columns> 

    <columns>CORE.USERS.MIDDLE_NAME</columns> 

    <columns>CORE.USERS.CELL</columns> 

    <columns>CORE.USERS.COMMUNITY_NICKNAME</columns> 

    <columns>OOO_End_Date__c</columns> 

    <columns>OOO_Start_Date_Time__c</columns> 

    <columns>CORE.USERS.PHONE</columns> 

    <columns>Planned_Activation_Date__c</columns> 

    <columns>CORE.USERS.STATE_CODE</columns> 

    <columns>CORE.USERS.SUFFIX</columns> 

    <filterScope>Everything</filterScope> 

    <label>testing list view 2</label> 

    <sharedTo> 

        <allInternalUsers></allInternalUsers> 

    </sharedTo> 

</ListView> 

Based on this, I have two questions:

1. Is there a programmatic way to retrieve only the specific fields that are available for selection when creating a User List View in the standard Salesforce UI?
2. Is there an official documentation page or mapping matrix I can refer to that translates standard SOQL field API names to these specific Metadata API names?

#Salesforce Developer  #TrailblazerCommunity  #Apex