Skip to main content
注目のグループ

Datablazer Community Group

Welcome, Datablazer! Are you ready to unlock the full potential of all your data and join a community of like-minded visionaries? Welcome to the Datablazer Community, where IT and business leaders, developers, and data practitioners come together to transform data into their most powerful asset.

Datablazers, we’re taking the big stage at Dreamforce!

 

In just a couple weeks, we’ll be talking about a challenge I know a lot of us are thinking about: AI is moving fast, but it’s only as good as the data and context behind it. 

 

Join us live or tune in virtually to the Data 360 Keynote to see how our latest innovations can help you get it right. 

 

🗓️ Wednesday, September 16 | 3:45 PM PDT 

📍 Moscone West, L3, Room 3001 

 

We don’t want to give away all the surprises just yet, but trust us… you’re going to want to be in the room for this one. We have some special moments planned for you! Come ready to learn, get inspired, and see our community show up on one of the biggest stages. 

 

I’ll see you there! 

 

Add it to your Dreamforce schedule: https://sforce.co/4wPeDbV

 Experience  #DF26 on Salesforce+: https://www.salesforce.com/plus 

1 件のコメント
0/9000

Your data is the foundation. Developers are building what comes next. 📊

Datablazers: get a first look at how Headless 360 and AI-powered innovations are helping developers build connected experiences with Salesforce data at the #DF26 Developer Keynote. 

 

⏰ Sept 17 | 9:00 a.m. PT 

📅 Add to your in-person agenda: sforce.co/3UdjR3y

💻 Stream on Salesforce+: sforce.co/46cH7RXYour data is the foundation. Developers are building what comes next.

0/9000
5 件の回答
  1. 9月3日 13:19

    Thanks so much I will add to my favourites. I'm still at the foundational level when it comes to data cloud knowledge but I have an understanding of data concepts and data bases in general.

0/9000

⭐️ Master the Basics of Data Exploration with Data 360 Query Editor ⭐️ 

Ever wonder how to quickly pull the exact business answers you need? This module guides you step-by-step through the main features of the Data 360 Query Editor. You will learn how to create your workspace, run simple queries, and pull the exact information you need without getting overwhelmed.  

👉  Complete this Trailhead Module 

⭐️ Master the Basics of Data Exploration with Data 360 Query Editor ⭐️ Ever wonder how to quickly pull the exact business answers you need? 

1 件のコメント
0/9000

⭐️  NEW: Data 360 August Monthly Release Summary 

⭐️  

Here are the new Data 360 features released in August ’26.

👉  Our August release notes are split across two releases: find the Summer '26 release notes here, and the Winter '27 release notes here

⭐️ NEW: Data 360 August Monthly Release Summary ⭐️ Here are the new Data 360 features released in August ’26. 

0/9000
0/9000

Quick reminder: Datablazer Coffee Chat is happening tomorrow, Aug. 25 at 9 a.m. PT!

 

If you’re thinking through where you’re going with your data architecture before you start building the pipes, come join the conversation. We’ll be talking through what the architecture actually needs to enable, with plenty of space to ask questions, share what you’re working through, and learn from one another. 

 

Register here!

0/9000

📣 It's back. Mark your calendars, lace up your shoes, and get ready to run (or walk, or stroll with coffee in hand) through one of San Francisco's most iconic backdrops. 

 

Registration is officially open for the Annual Dreamforce Community Fun Run

 

We will once again meet up for an  at-your-own-pace 5K. Open to  ALL (Trailblazers, Customers, Partners), this beloved tradition brings together Trailblazers for a morning of movement, connection, and fun, plus limited swag for customers while it lasts. 

 

🗓️ Wednesday, September 16, 2026

📍 6:00 AM

📌 Ferry Building Marketplace 

🔗 https://invite.salesforce.com/df26communityfunrun

📍Run Route: https://success.salesforce.com/06930000005Q0j7

 

Important Notes: 

 

Start & Finish: The run will begin and end on sidewalk directly in front of the Ferry Building's main staircase (as is tradition), we'll loop around AT&T Park, and head back to the start. 

 

Bags: Please leave bags and personal belongings at your hotel. We do not have the ability to store or monitor bags. We are in a public space.

 

Notes: This is not timed and very informal.

 

Grab your spot, bring a friend, and help us make this year's run the biggest one yet. 

 📣 It's back. Mark your calendars, lace up your shoes, and get ready to run (or walk, or stroll with coffee in hand) through one of San Francisco's most iconic backdrops.

 

 

 

@New to Dreamforce  @Flyin' Solo  @WELLforce  @Fitblazer Community  @Dreamforce for Admins @Nonprofits at Dreamforce  @Trailblazer Community Cove  @MomentMarketer Community Group @All Dreamforce @* Salesforce Administrators * @Salesblazer Community Group @Serviceblazer Community Group @Commerce Trailblazers @Datablazer Community Group

8 件のコメント
0/9000

The Data 360 G2 Giveaway is officially closed! 🎉

 

A huge thank you to everyone who took the time to share their Data 360 experience on G2. We’ll be announcing the 25 Datablazer hoodie winners soon, so keep an eye on your inbox!

 

Thanks again to everyone who participated and shared their voice!

1 件のコメント
0/9000

We're syncing several tables from Amazon Redshift into Salesforce Data 360 via a Redshift Connector. Our initial ingestion consumed a large percentage of our Data Service Credits, so we're now trying to understand the credit implications of subsequent updates. 

 

Question:

If an entire source table in Redshift is updated (e.g., a bulk UPDATE that touches every row, or a full table rebuild/recreate), does the next Data 360 refresh treat this as a full re-ingestion — consuming roughly the same number of credits as the initial load? Or does Data 360's incremental sync still detect and ingest only the changed rows in that case? 

 

What we've already tried:

  • We've set up incremental sync using a datetime field per Salesforce's documentation.
  • We created Redshift views (rather than syncing raw tables directly) to limit scope and reduce transformation-related credit consumption, since we confirmed transformations also draw from the credit pool.

 

Additional question — guardrails: What's the recommended way to set up guardrails against unexpected credit overspend on Redshift-connected streams? Specifically: is there a way to cap or alert on credit consumption per data stream/connector, or to simulate/estimate credit cost before a scheduled refresh runs against a large or recently-modified table?

2 件の回答
  1. 8月21日 17:01

    Hey Thomas, 

     

    Yes, a bulk update that touches every row will trigger a full re-ingestion at roughly the initial-load cost. Incremental sync works off your cursor datetime field, it pulls any row where that field is newer than the last sync point. It doesn't diff actual content, so if every row's timestamp advances, every row looks new and gets re-pulled. A full table rebuild/recreate causes the same result. Ingestion is metered per row processed, so re-ingesting the full table costs close to the original load (upserts by primary key, so no duplicates, but you still pay to process every row). 

     

    To avoid this: only update the datetime field on rows that actually changed, leave others untouched, and avoid full table rebuilds/recreates for the same reason. 

     

    On guardrails: 

    - Digital Wallet is Salesforce's built-in credit tracking tool, shows real-time and historical usage by type, and supports threshold alerts (commonly set at 70-80%) so you're warned before a runaway refresh drains the pool. 

    - There's no native hard cap per stream/connector, alerts are the mechanism, not a stop-gap. 

    - There's no built-in cost simulator before a scheduled run. Estimate manually using row count × the rate-card multiplier for your usage type, and watch Digital Wallet trends after each run. 

    - Consider splitting high-churn tables into their own stream so a bad restamp event is easier to isolate and spot in reporting. 

     

    Reference:

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

0/9000