Skip to main content
추천 그룹

* CRM Analytics (fka Tableau CRM) *

Welcome! This group is dedicated to your success with Salesforce CRM Analytics. Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

We’re happy to share Winter ‘27 Release resources! 🩵 

 

 

🚨 BONUS: Get ready for FeatureFest at Dreamforce! 🚨 Discover what’s new in the Winter ’27 release, get personalized feature recommendations, connect with experts, earn exclusive swag, and leave ready to get more from Salesforce – all in one exciting Dreamforce experience. Stay tuned – we’ll share more details next week!

 

Release Matrix can be found here: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000pPZmY0AW

 

Overview deck can be found here: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000jASjE0AW

댓글 23개
0/9000
댓글 23개
  1. 9월 8일 오후 7:18

    It is published now.

0/9000

Excellent example for improving performance when using WhatsApp, especially for those with many agents using this tool. Enable subtitles in your language and 1080p quality

 

https://www.youtube.com/watch?v=kHTemjVWEG0&list=PLYStC_2TZBSU

  

Excellent example for improving performance when using WhatsApp, especially for those with many agents using this tool. Enable subtitles in your language and 1080p quality: https://www.youtube.

 

 

0/9000

Hi,  

 

I would like to know if we can embed a External Dashboard into Salesforce. We have a looker dashboard that sources data from multiple places. How do I expose  per account on SFDC or a Wholistic view. Or Should I have recreate all in CRM Analytics?  

 

Thanks In Advance 

@* CRM Analytics (fka Tableau CRM) *

답변 5개
  1. 9월 7일 오후 3:29

    I’d probably keep the Looker dashboard if it’s already bringing together data from multiple sources. If the main goal is to give users an account-level view inside Salesforce, I’d first look at whether embedding the existing dashboard can meet that need before rebuilding everything in CRM Analytics.

    I’ve found this approach useful in other projects too. For example, with fit-out work, it often makes more sense to work with what’s already in place and improve the parts that need attention rather than starting everything from scratch.

0/9000

FeatureFest is coming BACK to Dreamforce for its second year!  

 

✨ Take a personalized feature match quiz and discover innovations tailored to your needs 

🎤 See what’s new in action with live demos 

📺 Join Release Readiness Live sessions throughout the day 

🎁 Grab exclusive swag (and some snacks!) 

 

📍 Moscone West, Level 2 

 

Come see what’s new. Find your next favorite feature. Get ready for what’s next.FeatureFest is coming BACK to Dreamforce for its second year! ✨ Take a personalized feature match quiz and discover innovations tailored to your needs 🎤 See what’s new in action with live demos 📺 Jo

댓글 5개
0/9000

Hi all, 

Recently I received an email from Salesforce on the subject I put in my header. I have read it several times and also clicked the added links but I cannot fully understand what the impact is here. 

Not sure if this is about External Connectors to other Salesforce Orgs only or if it also about External Connectors to an Azure SQL database. 

Also I am a bit surprised about the seemingly short notice on this change. Does anyone else have similar questions and/or an answer to my question 

 

답변 2개
  1. 9월 7일 오전 7:23

    Thanks Gerry, 

    It's just that when this is for SF to SF connections only I would have expected the message to state that clearly. Probably the distinction between External connectors and Database connectors is what I should look at.

0/9000

Hello, 

 

I have an object "ProjectProduct" with fields "Project" and "ProductLine" with data like this :  

Project; ProductLine 

Project 1; PL4 

Project 1 ; PL6 

Project 1; PL6 

Project 1; PL9 

Project 2; PL1 

Project 3; PL1 

Project 3; PL5 

 

As you can see, a same product line could be displayed several times for a project. 

 

In the recipe, I want to :  

1) deduplicate the productLines for same project. In this exemple, PL6 for Project 1 has to be displayed once. 

2) For each project, I want to know the number of productline by project  :  

Project | number of productline 

Project 1 | 3 

Project 2 | 1 

Project 3 | 2 

3) For each project, I want to have the list of ProductLine with delimeter ";" 

Project | List productlines 

Project 1 | "PL4;PL6;PL9" 

Project 2 | "PL1" 

Project 3 | "PL1;PL5" 

 

Then in my dataset I need these values : 

Project | List productlines | number productlines 

Project 1 | "PL4;PL6;PL9"| 3 

Project 2 | "PL1" | 1 

Project 3 | "PL1;PL5" | 2 

 

Thank in advance for your help 

 

답변 3개
  1. 8월 27일 오후 3:03

    Oh - yes, forget the final step: 

     

    Use another multi-row formula: 

    partition by project, sorted by size desc 

    function row_number() will mark the row with the highest amount of values with 1 

    finally filter on this row_number = 1 

     

0/9000

Hi All, 

 

I have a requirement to provide

record-level access based on the role hierarchy. For this purpose, I have created list filters from the top-level role to the lowest level, such as Manager 1, Manager 2, … up to Manager 6.

However, I am facing the following issues while implementing this logic:

  • When I use a Left Join in the recipe, the recipe takes a long time to process and eventually fails. 
  • When I use Lookup (Multivalue), I receive the following warning: 

“One or more cell values of the Mgr4Name field exceeded 32000 characters in length and had to be truncated in node OUTPUT0.”

The Mgr4Name field contains not more than 1,906 characters, which is causing the multivalue field to exceed the 32,000-character limit.

I have attached the recipe screenshot for reference.  I have applied multivalue lookup join from 'Role ID Rung 1' to 'Role ID Rung 6' join.

Could you please suggest an efficient approach or alternative logic to implement the role-hierarchy-based record access while avoiding the 32,000-character truncation warning and ensuring the recipe completes successfully?

 

Warning exceeding 3200 for recipe 

image.png

 

답변 1개
0/9000

I am struggling with transforming a multivalue picklist into a new field to use in a recipe. Ultimately, I am trying to transform that multivalue field so I can do a count for each program of interest. However, in the very first transform node I am getting an error that says "Your formula uses a field that doesn’t exist. Update or remove the fields ;." 

 

I am using this video as guide to help with this -

https://www.youtube.com/watch?v=gEOsRYBdiQQ

. But I am really at a loss on why I am getting this error for the field that does exist and it is not letting me more forward in my recipe. 

  

Any insight on what settings I could be overlooking?  

 

Thank you!  

  

 

 

Trying to transform a multivalue field in a recipe

 

 

답변 7개
  1. 8월 20일 오전 2:27

    If that worked than you were creating a string from a multivalued, not creating a multivalue from a string.  Either way glad you git it :)

0/9000

Hello, 

I'm currently trying to create a date field in a dataflow to calculate the month end date 6 months prior to another field. For example: 

 

Existing_Date_Field

= 2026-06-30 

Desired_Result

= 2025-12-31 

 

I'm struggling to find a combination of functions that gets me this result. Has anyone tried to do something similar and could you share your SAQL expression?  

 

 

Thanks!

답변 9개
  1. 8월 5일 오후 8:40

    Posting a solution incase anyone is trying to solve the same issue in the future. It may not be the most simplified solution, but it does give the correct results: 

     

    month_last_day(toDate(

    (case

    when string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) <= 6

    then number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "yyyy")) - 1, "0000")

    else number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "yyyy")), "0000")

    end)

    + "-" +

    (case

    when string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) <= 6

    then number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) + 6, "00")

    else number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) - 6, "00")

    end)

    + "-" + "01",

    "yyyy-MM-dd"))

0/9000