Skip to main content

#Data Cloud76 utenti parlano di questo argomento

Hi Everyone, 

 

Could you please assist me about this Semantic Model Error "

An error occurred in Semantic Layer. TraceId: 625f999de597e45396ce7008b8c62eb6 Status: INVALID_ARGUMENT Error Message: QUERY_EXECUTOR|table "ssot__Account__dlm" does not exist Caused by: line 1, column 2420: ...yee_Count4" from "ssot__Account__dlm" as "Account4" li... ^~~~~~~~~~~~~~~~~~~~".

Thanks,

 

#Data Cloud

0/9000

We're in the process of connecting Salesforce Data Cloud to our WordPress marketing site to track web engagement — page activity, CTA clicks, and form fills. We want to capture behavioral data and properly identify visitors when they submit a form, so we can stitch browsing activity to an identified record. (All tied to our Marketing Cloud Next/Advanced platform analytics)    We're evaluating two paths and would love input from anyone who has been through this decision, particularly in a B2B context.     

 

Path 1 — GA4 Connector

Path 2 — Manual Web SDK with Sitemap     

 

Questions   

1. For a B2B site focused purely on page engagement and form fills, does the GA4 connector capture an equivalent level of behavioral data compared to a manually configured sitemap? Or are there meaningful gaps?     

 

2. Identity resolution is our biggest concern with the GA4 path. When a visitor submits a form, will the GA4 connector properly stitch that known identity (email) back to their anonymous browsing history?    

 

3. Are there any known data quality issues with the GA4 path — such as bot traffic inflating profiles?     

 

4. For those who've implemented the manual SDK: how complex was the sitemap build for a non-ecommerce site? We'd need to cover page type definitions, button/CTA clicks, and form submission events (for our MCA forms)       

 

@* Data 360 *

  

 

#Data Cloud

3 risposte
  1. Ieri, 14:54

    Has anyone here had success creating similar web tracking activity that Pardot(AE) captured? I.E., referrer, page visits in sequential order, all showing on the lead/contact records and used the Marketing Cloud Next forms.  

     

    I'm having trouble capturing this data on the lead/contact record and reading that hidden fields on the forms might be my only hope since I'm using the MC Next forms and I can't send an identity event from the SDK on our primary host domain since the form is MC Next is technically a subdomain so the primary domain can't read the email. 

0/9000

Trailhead ć®ćƒ¢ć‚øćƒ„ćƒ¼ćƒ«ć€ŒData Graphs in Data 360ć€ć®å˜å…ƒć€ŒCreate a Data Graphć€ć§ć€ćƒćƒ³ć‚ŗć‚Ŗćƒ³ Challenge ć«åˆę ¼ć§ććšå›°ć£ć¦ć„ć¾ć™ć€‚ 

 

ā–  č”Øē¤ŗć•ć‚Œć‚‹ć‚Øćƒ©ćƒ¼ 

Challenge は Data Cloud ć§ćÆć¾ć å®Œäŗ†ć—ć¦ć„ć¾ć›ć‚“ 

Make sure the my_test_dg data graph is saved, built, and active. If the Last Run Status still shows 'Processing', wait a few more minutes. 

 

ā–  ćƒ‡ćƒ¼ć‚æć‚°ćƒ©ćƒ•ć®ēŠ¶ę…‹ļ¼ˆData Graphs の一覧) 

惻Data Graph Label / API Name:my_test_dg 

惻Primary DMO:Individual 

惻Data Space:default 

惻Status:Active 

惻Last Run Status:Success 

惻Type:Standard Data Graph 

惻Schedule:Weekly 

惻Record Count:1,467 

 

ā–  ćƒ‡ćƒ¼ć‚æć‚°ćƒ©ćƒ•ć®ę§‹ęˆ 

惻Individual(主 DMOļ¼‰ļ¼šBirth Date态Created Date态First Name态Last Name 

惻Contact Point Address(Individual の下) 

惻Account Contact(Contact Point Address ć®äø‹ļ¼‰ļ¼šAccount态Contact Email态Last Activity Date 

 

ā–  å®Ÿę–½ć—ćŸć“ćØ 

ćƒ»ćƒ–ćƒ©ć‚¦ć‚¶ć®ć‚­ćƒ£ćƒƒć‚·ćƒ„ć‚ÆćƒŖć‚¢ 

ćƒ»ćƒ‡ćƒ¼ć‚æć‚°ćƒ©ćƒ•ć®å†ę§‹ēÆ‰ļ¼ˆSave and Build) 

ćƒ»ćƒ‡ćƒ¼ć‚æć‚°ćƒ©ćƒ•ć‚’å‰Šé™¤ć—ć€ę•™ęć®ę‰‹é †é€šć‚Šć«ä½œć‚Šē›“ć— 

惻Challenge ę¬„ć®ć€Œčµ·å‹•ć€ćƒœć‚æćƒ³ć‹ć‚‰é–‹ć„ćŸēµ„ē¹”ć§ä½œę„­ć—ć¦ć„ć‚‹ć“ćØć‚’ē¢ŗčŖ 

ćƒ»ć‚¹ćƒ†ćƒ¼ć‚æć‚¹ćŒ Active / Success ć«ćŖć‚Šć€å‡¦ē†äø­ć®ć‚¢ć‚¤ć‚³ćƒ³ćŒę¶ˆćˆć¦ć‹ć‚‰ Challenge ć‚’ē¢ŗčŖ  

惻Trailheadć‚’čØ€čŖžčØ­å®šć‚’č‹±čŖžć«å¤‰ę›“ć—ē¢ŗčŖ

 

ā–  ē’°å¢ƒ 

惻Data Cloud Playgroundļ¼ˆęœŸé™ļ¼š2026/10/20 午前9:00 JST) 

 

åŒć˜ē¾č±”ć«é­é‡ć•ć‚ŒćŸę–¹ć‚„ć€č§£ę±ŗę–¹ę³•ć‚’ć”å­˜ć˜ć®ę–¹ćŒć„ć‚‰ć£ć—ć‚ƒć„ć¾ć—ćŸć‚‰ć€ć”ę•™ē¤ŗć„ćŸć ć‘ć¾ć™ćØå¹øć„ć§ć™ć€‚ 

ć‚ˆć‚ć—ććŠé”˜ć„ć„ćŸć—ć¾ć™ć€‚ 

Trailhead怌Create a Data Graphć€ć® Challenge が Active ć§ć™ćŒåˆę ¼ć—ć¾ć›ć‚“image.png

 

image.png

 

#Trailhead Challenges  #Trailhead  #Data Cloud  #Data360  #Salesforce Developer  #Salesforce_developer

1 risposta
0/9000

Hi Trailblazers, 

 

I recently started learning about Salesforce Data 360 on Trailhead.

From what I understand, Salesforce CRM already stores customer information in objects like Accounts, Contacts, and Opportunities.

Data 360 also works with customer data from different sources.

My question is, if customer information is already available in Salesforce CRM, why do companies need Data 360?

Can someone explain with a simple real-world business example? 

 

Thanks for sharing your knowledge! 

 

#Data Cloud

1 risposta
  1. 19 ott, 10:40

    Hi @Chaitanya d

    Good question! Salesforce CRM and Data 360 both work with customer data, but they serve different purposes. 

     

    1. Salesforce CRM – Manage Customer Relationships

    • Stores Accounts, Contacts, Leads, Opportunities, and Cases.
    • Helps Sales and Service teams manage daily business activities.
    • Mainly works with customer information available in Salesforce.

    2. Data 360 – Unify Customer Data

    • Connects customer data from Salesforce and external systems.
    • Uses Identity Resolution to link records belonging to the same customer.
    • Creates unified customer profiles.
    • Supports segmentation, insights, personalization, and AI use cases.

    3. Simple Real-World Example

    Consider an e-commerce company:

    • Salesforce CRM: Stores customer contact details and support cases.
    • Website: Stores browsing activity.
    • Order Management System: Stores purchase history.
    • Marketing System: Stores campaign interactions.

    Without Data 360, this information may remain in separate systems.

    With Data 360, the company can connect these sources and build a unified customer view.

    For example, when a customer contacts support, the agent can see their purchase history, recent interactions, and support cases if those data sources are connected and configured. 

     

    4. When Do We Need Data 360?

    • When customer data exists across multiple systems.
    • When we need Identity Resolution and unified profiles.
    • When businesses need advanced segmentation and personalized experiences.
    • When Agentforce needs additional customer context from multiple sources.

    If your requirement is simply managing Accounts, Contacts, Opportunities, and Cases, Salesforce CRM may be enough.

    If your requirement is connecting data from different systems and creating a unified customer view, Data 360 becomes valuable. 

     

    Simple Difference:

    Salesforce CRM = Manage customer relationships.

    Data 360 = Connect, unify, and activate customer data. 

     

    Salesforce Documentation:

    Related Trailblazer Discussions:

    1. Why Do We Need Data Cloud When We Already Have Data Storage?
    2. Data Cloud vs CRM Analytics
    3. How Does Data 360 Help Agentforce?

    Hope this helps you understand the difference!

0/9000

Builder Central (Beta) shows "Failed to fetch" on the welcome screen in my Agentforce Developer Edition org. 

Console: CORS preflight to

https://api.salesforce.com/platform/dx-workspaces-proxy/v1/api/workspaces-proxy/<workspaceId>/project-service/v1/projects

 

is blocked. The OPTIONS response is HTTP 204 with no Access-Control-Allow-Origin header. 

Reproducible with curl from outside the browser for any Origin, so it is not a client-side issue. 

"Connect an org" logs in successfully but never returns to the app. 

Org: nexustrade-portal-dev-ed, Home Org ID 00DgK00000WFVD2. Workspace ID: b6f6c7b9-dd87-4ca5-99e9-0d74efb79d36. 

 

Builder Central (Beta) shows

 

 

image.png

 

 

 

I have followed the steps - 

  1. enable data cloud - https://help.salesforce.com/s/articleView?id=data.c360_a_setup_provision.htm&type=5
  2. enable einstein AI from einstein setup - https://help.salesforce.com/s/articleView?id=ai.generative_ai_enable.htm&type=5
  3. enable agentforce - 
  4. enable builder central
  5. assign permission set - Access Builder Central
  6. launch the builder central(beta) from setup

 

 

 

#Agentforce  #Salesforce Developer  #Data Cloud  #AI

5 risposte
0/9000

Salesforce Developer Roadmap in the AI Era (2026–2027) 

 

Hi Trailblazers, 

 

With Agentforce, Data 360, and AI becoming part of Salesforce development, I believe developers need to strengthen their core technical skills while learning new AI capabilities.

Here is my suggested learning roadmap for beginners and working professionals. 

 

1. Salesforce Fundamentals

  • CRM basics, Objects, Fields, and Relationships
  • Security, OWD, Profiles, and Permission Sets
  • Flow Builder and Validation Rules

Salesforce Developer Beginner

 

2. SOQL & Apex Development

  • SOQL, SOSL, and Relationship Queries
  • Apex Classes, Triggers, and Collections
  • Bulkification, Governor Limits, and Test Classes

Apex Basics

 

3. Lightning Web Components (LWC)

  • HTML, CSS, and JavaScript
  • Components, Events, and Data Binding
  • LWC with Apex and Lightning Data Service

LWC Developer Guide

 

4. Salesforce Integrations

  • REST APIs, JSON, and OAuth 2.0
  • Named Credentials and Apex Callouts
  • Platform Events and Asynchronous Apex

Apex Integration Services

 

5. Salesforce DevOps

  • VS Code, Salesforce CLI, and Git
  • Sandboxes, Deployments, and Testing
  • CI/CD and DevOps Center

Salesforce CLI

 

6. Agentforce & AI Development

  • Agentforce Builder, Subagents, and Actions
  • Agent Script and Prompt Builder
  • Apex and Flow Actions for AI Agents
  • Agent Testing, Security, and Debugging

Agentforce Developer Guide

 

7. Data 360

  • Data Streams and Data Lake Objects
  • Data Mapping and Identity Resolution
  • Data Graphs, Retrieval, and Agentforce Grounding

Data 360 Learning

Data 360 Overview – SFDCINDIA

 

8. Real-World Projects

Build at least three practical projects:

  1. Student Management System – Admin, Apex, and LWC
  2. Customer Support Application – Flow, Integration, and Security
  3. AI Customer Support Agent – Agentforce, Actions, and Data 360

My Suggestion:

Don't jump directly into Agentforce without understanding Salesforce fundamentals.

Learn Salesforce → SOQL → Apex → LWC → Integration → DevOps → Agentforce → Data 360

AI can help developers write code faster, but understanding business requirements, architecture, security, debugging, and testing will remain essential.

My Key Point: The future belongs to developers who understand both Salesforce Development and AI.

What skills are you focusing on to stay relevant in the AI era? 

 

Venkat Yadav | SFDCINDIA

#Salesforce Developer #Salesforce Admin #Agentforce #Data Cloud #TrailblazerCommunity #Trailhead Challenges

1 commento
0/9000

Hi Trailblazers!  

 

If you're planning to learn Salesforce Data 360 (formerly Data Cloud), here is a simple roadmap to follow.

1. Data 360 Basics

  • Introduction, Architecture and Real-Time Use Cases
  • Key Features and Benefits

2. Setup and Data Ingestion

  • Data 360 Setup and Permissions
  • Data Spaces, Data Streams and Connectors
  • Zero Copy Integration

3. Data Modelling

  • Data Lake Objects (DLOs)
  • Data Model Objects (DMOs)
  • Data Mapping and Transformations

4. Identity Resolution

  • Matching and Reconciliation Rules
  • Unified Customer Profiles

5. Insights and Segmentation

  • Calculated Insights and Streaming Insights
  • Segments and Data Graphs

6. Data Activation

  • Activation Targets
  • Data Actions and Flow Integration

7. Data 360 with Agentforce

  • Structured and Unstructured Data
  • Search Indexes and Retrievers
  • Data Libraries and Agentforce Integration

8. Security and Practical Experience

  • Data Security and Governance
  • Monitoring and Troubleshooting
  • End-to-End Real-Time Project

 Useful Learning Resources 

 

šŸ”— SFDCINDIA – Salesforce Data 360 Blog

https://sfdcindia.com/blog/salesforce-data-360

 

šŸ”— Salesforce Data 360 Learning Trail

https://trailhead.salesforce.com/content/learn/trails/data-cloud-explore-setup-to-activation

 

šŸ”— Data 360 Fundamentals

https://trailhead.salesforce.com/content/learn/trails/unlock-your-data-with-data-cloud

 

šŸ”— Salesforce Official Documentation

https://help.salesforce.com/s/articleView?id=data.c360_a_data_ingestion.htm&type=5

 

šŸ”— Data 360 Consultant Certification

https://trailhead.salesforce.com/credentials/data360consultant

 

My Suggestion:

Start with Data Streams, DLOs, DMOs, and Data Mapping before moving to advanced topics.

Focus on hands-on practice and try to build at least one end-to-end project. 

 

 Which Data 360 topic do you find most challenging? 

 

Let's share our experiences and learn together! 

 

#Data Cloud #Data360 #Agentforce #Trailhead Challenges #TrailblazerCommunity

0/9000

Good afternoon everyone, how are you? 

 

We have some questions regarding the Repeater Block and its pre-configuration. We saw in a documentation that it was necessary to force a relationship between our Products DMO and the Individual to be able to associate it with the Data Graph, and then personalize our abandoned cart emails. 

 

The question we have is:  

 

Is this step of forcing a relationship really necessary? Or do we need a separate Data Graph for each function? Will each Data Graph work as an activation (comparing it to the use of Data Cloud activation to MCE) ? 

 

 

Thank you.

 

 

 

Repeater Block - MC Next

 

 

 

#Trailhead Challenges  #Trailhead  #Salesforce Developer  #Salesforce Admin  #Salesforce  #TrailblazerCommunity  #Data Cloud

2 risposte
  1. 15 ott, 15:18

    @Matt Thomas

    I have a few final considerations, if you could help me:  

     

    1 - When you mention "product", are you referring to the Product Catalog DMO or Shopping Cart Product Engagement? 

     

    2- Do we need to create a relationship linking Shopping Cart Product Engagement to the Product DMO?

     

    3- Individual > Shopping Cart Engagement > Shopping Cart Product Engagement > Product. Is this the expected structure? Or does there need to be a direct relationship between Product and Individual? Can it be indirect?

0/9000

Hi Trailblazers, 

 

Salesforce Data 360 helps businesses bring customer data from different sources into one place. 

 

But I'm interested in understanding its real value beyond data integration. 

 

From your project experience, which features provide the most business value: Identity Resolution, Data Graphs, Segmentation, or real-time data activation? 

 

How important is Data 360 for making Agentforce agents more accurate and useful? 

 

Would love to learn from your implementation experiences. 

 

#Data Cloud #Agentforce  #Data360

1 risposta
  1. 15 ott, 08:39

    Hi @Galla Rajeswari Good question! Data 360 is not just about combining data. It helps businesses use customer data more effectively.

    1. Identity Resolution: Combines customer records to create a unified customer profile.
    2. Data Graphs: Connect related data and help Agentforce access customer information faster.
    3. Segmentation: Helps businesses identify and target the right customers.
    4. Real-Time Activation: Helps businesses take action using updated customer data.
    5. Agentforce: Provides better customer context, helping agents give more relevant and accurate responses.

    In my view, Identity Resolution and Data Graphs are especially useful for Agentforce.

    Key Point: Data 360 provides the right customer context, while Agentforce uses that data to answer questions and perform actions.

0/9000
1 risposta
  1. 14 ott, 22:58

    @Saurabh Singh

     

    It seems the index configuration was completed at the metadata level, but the underlying chunk table was never physically created or materialised.  

    Try below -  

    Delete and recreate the Search Index rather than querying the chunk table directly. The chunk DMO isn’t meant to be hand-queried in Data Explorer as your primary check anyway, recreating forces the chunk table to rebuild. Confirm the source DMO has rows first. 

     

    Verify the source DMO (KnowledgeArticleVersion__dlm) is populated and mapped before rebuilding. No source content, no chunk table. 

     

    Since this is a vector/Search Index feature that’s still maturing in Data Cloud, if the source has data and a clean rebuild still leaves the chunk table missing, treat it as a platform provisioning issue and raise a case with the TraceId from your error (33aa86a19608e2b0). That TraceId lets Salesforce pull the exact failure in the chunking/embedding job server-side, which is the one thing none of us can see from the UI, the Ready status is hiding whatever actually failed underneath. 

     

0/9000