🤔 Thursday Thought Starter: If you had to choose one, would you rather have:
A) Twice as much data
B) Half the data—but all of it trusted and high quality
Why?
🤔 Si pudieras diseñar una solución logística ideal en Salesforce, ¿qué características consideras imprescindibles?
Esta pregunta ha sido una de las principales motivaciones detrás de Logifresh, el proyecto que actualmente estoy desarrollando.
Me gustaría conocer la opinión de la comunidad, recibir una retroalimentación aprender de quienes tienen experiencia en el ecosistema Salesforce.
Los comentarios y sugerencias son más que bienvenidos. Quedó atenta saludos cordiales.
(Nota: escribo en inglés y usé un traductor, ya que no hablo español. Disculpen cualquier error.)
¡Qué buen proyecto, Logifresh! Desde mi experiencia, una solución logística ideal en Salesforce debería cubrir:
Visibilidad en tiempo real:
integración con GPS/telematics y APIs de transportistas, mostrada en un mapa en vivo. Para producto fresco, sensores IoT de temperatura/humedad con alertas por umbral son clave.
Optimización de rutas:
ruteo dinámico según tráfico, ventanas de entrega y capacidad del vehículo (Salesforce Maps Advanced o un motor externo).
Modelo de datos sólido:
objetos de Envío, Ruta, Parada, Vehículo y Conductor, con prueba de entrega (firma/foto) desde una app móvil.
Sincronización con inventario/WMS/ERP:
integración bidireccional (MuleSoft o platform events) para mantener stock y pedidos consistentes.
Gestión de excepciones:
Flows para reasignar entregas fallidas, alertas de SLA y notificaciones automáticas al cliente. Aquí es donde se gana o se pierde.
Trazabilidad y cadena de frío:
control de lotes, registro de temperatura y reportes para normativa de seguridad alimentaria.
Portal para el cliente:
Experience Cloud con ETA en vivo, link de seguimiento y reprogramación de entregas.
Analítica:
dashboards de entregas a tiempo, costo por km, mermas y desempeño de conductores.
Y sobre todo: diseño mobile-first y con soporte offline para conductores en zonas de baja señal. ¡Éxitos con el desarrollo!
Hi folks,
I am working on data cloud connectors.I am having problems especialy beta ones (GA4, YouTube Analytics) Is there anyone to share their experience / best practice for it?
Start by checking that all required permissions and API credentials are set correctly for the connector. Since GA4 and YouTube Analytics are beta connectors, they may have known limitations or intermittent issues.
Try reconnecting the data source, test with a small dataset, and review the connector logs for any errors. If the issue is only with the beta connectors, it's likely a beta-related limitation, so checking the latest Salesforce documentation or opening a Salesforce Support case is the best next step.
📊 Datablazers, are you ready to learn the fundamentals of building smarter AI agents with your data? 🤖
Join our FREE, expert-led Agentforce Builder Fundamentals workshop on Wednesday, July 15 and learn the fundamentals of building AI agents. Explore how Agentforce combines natural language, topics, actions, data, and Agent Script as you build, test, and refine an employee agent.
See how trusted Salesforce data and Agentforce Builder work together to create grounded, scalable AI experiences.
Save your spot at the time that works for you.
👉 1:30 p.m. AEST ➡️ https://invite.salesforce.com/APACbuilderfund
👉 10:00 a.m. EDT ➡️ https://invite.salesforce.com/builderfundamentals
actualmente estoy cursando ingenieria en desarrollo de software.....
Hi, Te recomiendo que te enfoques en construir una base sólida en lugar de intentar aprenderlo todo a la vez. Si quieres continuar tu trayectoria en Salesforce:
Y lo más importante: sé constante. Salesforce es un ecosistema enorme y nadie lo sabe todo. Concéntrate en aprender un poco cada día, desarrolla proyectos reales y sigue mejorando. Tu primera oportunidad suele surgir al demostrar tus habilidades y perseverancia, más que al tener años de experiencia.
🏕 It's Trailhead Tuesday: Customer Context and Profile Unification Fundamentals
AI is only as powerful as the customer context behind it. If you've ever wondered how organizations create a single, trusted view of the customer across multiple systems, this Trailhead module is for you.
In this module, you'll learn:
Whether you're new to Data 360 or looking to strengthen your understanding of customer data strategies, this module provides foundational knowledge you'll use again and again.
Already completed this module? Share a screenshot of your badge in 🧵
When you're dealing with old records, do you treat it as purge vs. archive differently depending on whether it's a retention/compliance requirement versus just general cleanup and storage hygiene? Would love to hear how that decision actually gets made and executed - native tools, custom Apex, something else?
@jake finegold happy to help, also worth noting Own is now Salesforce-owned (acquired late 2024), so Archive is really a first-party option now and on your question: yes, Archive handles the delete side too, retention policies do time-based deletion as part of the archive lifecycle, and purge policies let you force removal for things like right-to-be-forgotten. So it's not just archive/retrieval, deletion is built into the same policy engine. For pure hygiene deletes with no keep-requirement, though, most teams still just use native Bulk API / batch Apex, no need to bring Archive into it.
A topic of using Confluence in conjunction with our Salesforce org has come up. I've seen a handful of use cases, such as creating Salesforce Knowledge articles from Confluence pages. I'm looking for use cases within Sales Cloud and potentially MC Account Engagement.
Thanks in advance!
We've taken a similar approach. Confluence has worked well for maintaining playbooks, SOPs, onboarding material, and other internal documentation, while Salesforce remains the system of record for customer data.
One thing we found useful was keeping document generation inside Salesforce instead of managing those files in Confluence. 360 SmartDocs is one of the AppExchange solutions that supports that use case, so Confluence stays focused on knowledge management while documents like proposals and agreements are generated directly from Salesforce.
If you're exploring different options, here's the AppExchange listing I came across: https://appexchange.salesforce.com/appxListingDetail?listingId=994f0c85-2adb-4c30-9e67-40f391c1fc2a
New Trailhead Badge: Customer Context and Profile Unification Fundamentals
This new, community authored badge has gone live on June 15, 2026 to help guide your and your stakeholders' journey.
Achieve a contextual understanding of your customer based on complete understanding of their interactions.
Complete it, if you like it - promote it, if you have concerns, share your feedback here.
cc:
@* Data 360 *, @* Data Cloud for Marketing (fka CDP) *, @Data Quality & Management, @Agentblazer Community Group