Level Up Josh - Knowledge Drop

The Case for a Healthy Ego

rei.r.joshua@gmail.com (Rei) — Sat, 31 May 2025 19:14:54 GMT

Mention the word ego, and most people think of arrogance—someone who steamrolls meetings, flexes their knowledge, and needs to be the most intelligent person in the room. That kind of behavior? It's real. I've seen it. But it reflects only one extreme version of ego—not the whole picture.

Like most concepts, the impact of ego depends entirely on the individual and how they choose to express it.

Ego, when harnessed with empathy and purpose, isn't something to suppress—it's a tool you can wield. Like Uncle Ben says to Peter Parker, "With great power comes great responsibility." The same goes for ego: used thoughtlessly, it burns bridges and undermines others' confidence. Used with intent and purpose, it can enhance your ability to perform your job confidently every day.

Many professionals shy away from their ego, often because they don't understand what a healthy dose of good ego can do for them. First, let's take a moment to reframe what ego is. Ego comes from the Latin for "I" or "self." In psychology, it refers to the process of navigating between our identity, emotions, and the world around us. In more general terms, it relates to your sense of self-worth, self-esteem, and self-identity. It's the internal portrayal that shapes how you see yourself—and how you hope others see you.

So, what does a healthy, purposeful ego look like in action? Let's break it down because when paired with empathy, ego doesn't just elevate you; it amplifies how you show up for others.

Self-Esteem

Confidence in your abilities lets you speak up confidently, take initiative, and challenge the status quo. Paired with empathy, that confidence supports and lifts others rather than steamrolling them.

Self-Worth

Believing your voice matters fuels resilience. When you recognize and respect your contributions, you're more open to feedback because you don't feel threatened by it.

Self-Identity

Knowing who you are helps you stay grounded when things get chaotic. It brings consistency to your work and integrity to your decisions. With empathy, that identity isn't rigid; it's collaborative.

Confidence & Leadership

A healthy ego allows you to lead with clarity without overpowering those around you. Outstanding leadership isn't about being the loudest voice in the room; it's about creating an environment where others feel empowered to speak and take action. Confidence gives you the presence to make tough calls and speak with conviction; tempered with empathy, it ensures you listen with intention. When ego is grounded in purpose rather than pride, it fuels calm under pressure, consistency in vision, and the strength to stand firm.

An individual's ego becomes dangerous when driven by insecurity or a sense of superiority. But when rooted in clarity and conscious thought, it empowers you—and everyone around you.

Let me ground that in practical experience. I've been in the technology sector for a while. As a Technical Architect, I've seen what a healthy ego can do when it's not about being the loudest voice in the room—but the one people trust to speak with clarity and conviction.

Take high-stakes client reviews. I don't back down from what I know to be the best practice to save time or money. I speak confidently and clearly about what I believe is right for my clients. But I also realize in real-world scenarios, we must be flexible and adapt to the specific situations each client may be experiencing. It's not about winning; it's about finding the middle ground between what is optimal and what is practical. My ego gives me the presence to guide the room and the perspective to keep everyone aligned on what matters: long-term value.

Mentorship is another space where ego can shine or implode, depending on how it's applied. I don't mentor to boost my status. I mentor because I've been where others have. I know the grind. My ego is what tells me I can help them build their confidence and grow. And my empathy makes sure I'm listening as much as I'm leading.

Fourteen years ago, I held an associate's degree and worked in a call center with no benefits, no roadmap, just a drive to be better tomorrow than I was today. Today, I'm a Technical Architect working with global brands and building enterprise-grade solutions across multiple technology stacks. Two years ago, I jumped into a new technology and a new, strictly typed language. Something I had never done and had no traditional experience with; I not only made the transition, I thrived.

How was I able to do all these things over the last fourteen years?

Simple, I outworked everyone. I showed up early, stayed late, asked every question, made mistakes, took feedback, built trust, and never stopped learning. "My ego didn't whisper, 'You're better than this.' It shouted, 'You can be one of the best if you're willing to earn it.'"

Ultimately, ego isn't the enemy. It's the part of you that believes you're capable of achieving greatness and refuses to quit until you do.

Records and Relationships the DNA of Salesforce

rei.r.joshua@gmail.com (Rei) — Sat, 05 Oct 2024 02:27:56 GMT

When you hear Salesforce, you probably think of a massive, all-encompassing SaaS provider tailored for enterprise clients. You envision dashboards, reports, accounts, and sales opportunities—all seamlessly connected within complex business processes. Teams of professionals interact with the system daily, weaving their tasks into Salesforce’s vast landscape.

But beneath this complexity lies a simple, elegant structure that powers everything. In this article, we’ll strip away the layers to focus on Salesforce's fundamental building blocks—its DNA: objects, records, and relationships.

What Are Salesforce Objects?

At the core of Salesforce’s functionality is a system of Records and Relationships that powers the broader ecosystem. To fully understand how this system works, we must begin with the foundational element: the Salesforce Object.

A Salesforce object is like a technical blueprint. It defines the characteristics and structure of every record within Salesforce, whether it's an Account, Opportunity, or Lead. Each object has its unique set of fields, validation processes, and data types. For example, one object might allow users to select from a list of options, while another might need to store numerical data.

To make this more straightforward, let’s take a look at a simplified Account object that defines three basic fields:

Id (Auto Defined Id)
Name (Text Field)
Status (Picklist)

Using this Account object blueprint, you can create individual records, like the two below:

Account Record One
Id: 00001
Name: Acme Corporation
Status: Active
Account Record Two
Id: 00002
Name: Skynet Incorporated
Status: Deactivated

These aren’t just templates—they’re fully realized data entries that populate Salesforce, representing real-world entities like the businesses you work with. Salesforce's power comes from how these objects form the backbone of your operations, allowing you to collect, store, and access critical information.

Object Relationships: Connecting the Dots

Salesforce objects don't exist in isolation; the real magic happens when you connect them. This is where Object Relationships come into play, allowing you to link different records and create a web of interconnected data that mirrors your business processes.

Think of object relationships as the ties that bind in a family tree. Each person (or record) has unique information but is connected to others—parents, children, and cousins. These relationships provide context and depth, showing how different records are related.

In Salesforce, these relationships are essential to efficiently organizing and accessing your data.

Types of Object Relationships

There are two main types of object relationships in Salesforce: Lookup Relationships and Master-Detail Relationships . These relationships define how records connect and interact with one another.

Lookup Relationships

A Lookup Relationship is the simplest way to link two objects together. For example, consider an "Account" object and a "Contact" object. Each Account might have multiple associated Contacts, but those Contacts can also exist independently. The relationship provides context without creating dependence.

For example:

You have an Account record for "Acme Corporation."
You have a Contact record for "John Doe."

Creating a Lookup Relationship allows you to associate John Doe with Acme Corporation while still allowing him to exist as a stand-alone contact in other contexts.

Master-Detail Relationships

A Master-Detail Relationship is a tighter, more dependent connection. In this case, one object (the "Detail") cannot exist without the other (the "Master"). If the master record is deleted, the associated detail records are also removed because they rely entirely on the master for context.

Consider an example where you have an "Order" object and an "Order Line Item" object. Each line item exists within a specific order. If you delete the order, its line items are also deleted because they cannot exist independently. This structure helps maintain data consistency when one record type is directly dependent on another.

Why Object Relationships Matter

Object relationships are crucial for several reasons. First, they allow you to maintain data integrity and consistency. Without relationships, your records would be fragmented, making it hard to see how different business entities—like Accounts, Contacts, or Orders—are connected.

Second, relationships enhance reporting capabilities. When the right connections are in place, you can pull in data from related objects and create comprehensive reports that give you a more complete view of your business operations.

Finally, relationships improve usability. Salesforce’s interconnected structure lets users view related records in a single interface. For example, a sales rep can view all contacts associated with an account, see all orders tied to those contacts, and drill down into specific details without leaving the Salesforce ecosystem.

Hierarchical and Many-to-Many Relationships

In addition to Lookup and Master-Detail relationships, Salesforce offers other relationship types that cater to more specific needs.

Hierarchical Relationships

A Hierarchical Relationship is unique to the User object and allows you to create a hierarchy among users, helping to define organizational structures. For instance, you can set up reporting lines within your company, clarifying who reports to whom. This can influence data visibility and reporting, ensuring the right people can access the correct information.

Many-to-Many Relationships

Salesforce also supports Many-to-Many Relationships, which can be established using a junction object that connects two other objects. This type of relationship is useful when you need to associate multiple records from one object with multiple records from another.

For example, imagine you have two objects: Projects and Employees. Each project can have multiple employees assigned to it, and each employee can work on multiple projects. A many-to-many relationship allows this interaction, making it possible to manage more complex data models in Salesforce.

Salesforce Data Webs: Bringing It All Together

Understanding and leveraging object relationships allows you to transform isolated data points into an interconnected web of information. This network simplifies your business processes and enhances your ability to retrieve, analyze, and act on data in Salesforce. Whether building a simple Lookup Relationship between Accounts and Contacts or constructing a complex Master-Detail structure for Orders and Invoices, relationships are the glue that binds your Salesforce system together.

Closing Thoughts: Understand the Fundamentals

At its core, Salesforce is a powerful, flexible tool because of its foundational building blocks—objects and relationships. Mastering these elements is critical to unlocking its full potential. Whether you're streamlining your sales process, managing customer data, or building custom solutions, understanding Salesforce's DNA will allow you to create efficient, scalable systems tailored to your business needs.

Platforms Rise and Fall, but Architecture and Solution Design Endure

rei.r.joshua@gmail.com (Rei) — Fri, 27 Sep 2024 02:46:35 GMT

2024 has been a year of uncertainty and change, particularly in the e-commerce sector. As a committed professional in this field, I've witnessed the rise of AI, a significant topic in many industries, often more about hype than substance. AI's application has led to noise and confusion. Our industry has also experienced considerable attrition for many technology professionals as companies look to restructure and downsize following a partially artificial rise in hiring during COVID-19.

With a significant portion of my career dedicated to Salesforce Commerce Cloud (formerly Demandware), I bring a wealth of experience and insights to the ongoing discussion. As a seasoned member of the Salesforce community, I can provide reassurance and guidance on the best options for current Salesforce Commerce Cloud engineers to future-proof their careers.

"What is the best option for current Salesforce Commerce Cloud engineers to future-proof their career?"

This article aims to answer the question and introduce a more fundamental career philosophy that can enlighten and empower your decisions in the e-commerce sector.

My Journey from Salesforce Commerce Cloud to Core

Two years ago, when I assessed the current state of technology in e-commerce, I saw the writing on the wall: a reduction in direct updates and support for Salesforce Commerce Cloud, an aging technology stack, and infrastructure outside of Salesforce proper. These factors, combined with quick continued innovation by competitors in the commerce space, such as Shopify, led me to consider where to expand my skill set next.

Fortunately, my current employer, Red Van, was looking for a senior internal resource to dive into Salesforce Core Commerce (specifically B2B at that time). After taking some time to consider the various options and factors of leaving a product and stack I had spent the last 9+ years growing on, I decided to leap with both feet and trust that the skills I had been honing for all those years were more than just languages and specific technologies.

Over the next two years, I spent work hours and substantial personal time diving head-first into the Salesforce Core technology stack. Apex was my first taste of strictly typed language beyond a brief period of experimenting with TypeScript. I can honestly say that for two months, I loathed Apex more than any other language I have ever worked with. Everything about it felt obtuse and rigid. To a JavaScript developer, it felt unnatural in many ways. In those first months, there were many days when I sat there at the end of the day, cursing my decision to leave the relative comfort of Commerce Cloud and the familiarity of JavaScript.

Fast-forward to today. The project I am currently engaged in is a multi-cloud implementation that includes both Salesforce Core and Salesforce Commerce Cloud. This project involves integrating multiple Salesforce products and leveraging their unique capabilities to provide a comprehensive solution. The path I have taken and my choices have provided me with the unique capabilities to provide cross-cloud architecture insights and solutions. I can see the larger picture in a way I would never have been able to. Finding solutions across multiple technology stacks is invaluable to my client and my employer and, by extension, increases my value as an employee and partner.

Learning Salesforce Core is a Solid Option

To address the original question we asked ourselves at the start, beginning to learn Salesforce Core is a solid option. Now, let me be clear: When I say Salesforce Core, I mean starting with the fundamentals, not Commerce or any other specific product on the platform pure base Salesforce Apex, the data model, orgs, DX tooling, etc. Focusing on Commerce Core is too niche currently to justify your entire focus. Learning Salesforce fundamentals will, by its nature, extend to Commerce products and many others.

Focusing on Solution Design Skills is Better

Consider yourself a Salesforce Technologist or a Technologist with a current specialty in Salesforce. Your knowledge and abilities lend themselves to much more than a single product.

Why put yourself inside a box when you can focus on developing knowledge and skills that are far broader and resistant to career attrition?

My ability to understand fundamental commerce topics, such as a customer or order life cycle's, has served me well across Salesforce Commerce Cloud and extended to Salesforce Order Management, Core Commerce, and Shopify. These fundamental topics are universal in the e-commerce sector and understanding them allows me to design solutions that are not tied to any specific product.

While the underlying technology and systems for each product require specific knowledge, my ability to design Commerce solutions, see the bigger picture, and understand various interconnected systems and how they work together to make a robust enterprise system are skills that have little to do with the specifics of anyone product.

The longer my career goes on and the more knowledge and experience I accumulate, the more I believe that fundamentals are where we acquire the most value. Technology, language, and tools will come and go, adapt, and evolve, but the way we approach problems, the way we think through and design a solution, has remained fundamentally the same for hundreds of years.

Your Career is a Journey, Not a Sprint

The journey from a specialized Salesforce Commerce Cloud expert to a more diversified technologist embracing Salesforce Core and beyond has been challenging and rewarding. If 2024 has taught us anything, change is inevitable—whether in technology, market conditions, or career paths. Instead of resisting it, we should harness it, using our skills and experiences as the foundation for future growth.

In an industry where tools and technologies evolve constantly, more than relying on product-specific expertise is required. By focusing on broader skills like solution design, cross-cloud architecture, and a deep understanding of fundamental business concepts, we stay relevant and stand out as indispensable assets to our clients and employers. The ability to adapt, learn, and see the big picture will always hold more value than mastering the latest language or platform.

As you consider your path forward, remember that the most important skill you can cultivate is the ability to evolve continuously. By investing in foundational knowledge and staying flexible, you'll not only future-proof your career but also position yourself as a leader in the dynamic world of e-commerce technology.

FAQs

Is it necessary to switch to Salesforce Core to future-proof my career?

While not mandatory, expanding your skill set beyond a single platform, like Salesforce Commerce Cloud, to Salesforce Core offers more versatility and opportunities in the long term.

How can I get started with learning Salesforce Core?

Begin by diving into Apex, understanding Salesforce's data model, and familiarizing yourself with the platform's tools, such as Salesforce DX. Focusing on these basics provides a solid foundation upon which to build.

Can I still focus on e-commerce solutions while learning Salesforce Core?

Absolutely. E-commerce principles like customer and order lifecycle management remain relevant across multiple platforms. Learning Salesforce Core can enhance your ability to design cross-cloud solutions for various commerce products.

Should I focus on a niche like Salesforce Commerce Cloud or diversify my skill set?

Learning solution design, integration, and other platform capabilities diversify your skill set and make you more resilient to specific product or technology changes.

What if I don't like coding in Apex?

It's normal to struggle with Apex initially, especially if you're from a language like JavaScript. However, with time and practice, many developers grow comfortable with its structure and find that it enhances their problem-solving capabilities across Salesforce products.

A Salesforce Native Solution for Data Management

rei.r.joshua@gmail.com (Rei) — Tue, 24 Sep 2024 12:59:01 GMT

Salesforce Archive, unveiled at Dreamforce 2023, is the platform's latest offering designed to help organizations manage vast amounts of data. As the volume of business data grows, retaining and managing inactive or historical data becomes a challenge for many Salesforce users and a massive expense. Salesforce Archive offers a Salesforce native solution intended to help address these customer pain points by improving system performance, reducing storage costs, and ensuring compliance with data retention regulations.

Whether you're a Salesforce architect, developer, or an e-commerce professional, understanding how Salesforce Archive works and what it offers is crucial when considering it as an addition to your Salesforce solution.

The Launch of the Salesforce Archive

The Unveiling

During Dreamforce 2023, Salesforce introduced its native archiving solution. Among the many features showcased, Salesforce Archive immediately caught the attention of numerous current and potential Salesforce customers grappling with data overload. The product is currently in the pilot phase but is expected to become Generally Available (GA) shortly. This makes it a promising solution for businesses looking to alleviate the stress of managing their data and streamline their data management and retention infrastructure.

Current Pilot Program and Availability Timeline

The Salesforce Archive pilot program is ongoing and available to selected customers in several regions, including:

United States
Australia
Germany
India

This new offering is projected to be available in November 2024, and Salesforce plans to roll it out globally in phases. This pilot allows early participants to shape the product's features based on real-world feedback.

The Data Bloat Problem in Salesforce

Impact on System Performance

As organizations grow, their Salesforce environments become overwhelmed with inactive records, outdated files, and unnecessary attachments. This data bloat significantly impacts numerous system processes, such as slower queries, dashboards, and reports. These directly impact user productivity and, by extension, a client's ability to do business effectively.

Increasing Storage Costs

With Salesforce's on-platform tiered storage system, costs can quickly escalate, especially when you exceed your allocated limits. However, by leveraging Salesforce Archive, a native solution tailored for large-scale data storage, you can potentially reduce your on-platform storage footprint. This translates to significant cost savings, both in terms of required tiered storage and the additional costs associated with overages, providing a sense of financial security and confidence in your investment.

Data Governance Challenges

Many industries, such as healthcare and finance, face strict compliance and data governance rules. In these situations, hard Deletion is often not an option due to the need to retain data for regulatory reasons. Salesforce Archive offers a balanced approach, allowing customers to preserve data for future access without compromising the day-to-day performance of a production environment. This reassures users about the solution's effectiveness in managing data retention and system performance.

What is Salesforce Archive?

A Native Archiving Solution

Salesforce Archive is Salesforce's first native archiving solution. It enables organizations to archive inactive or historical records that need to be retained but are irrelevant to day-to-day operations.

Designed for Scalability and Efficiency

Explicitly built to scale with a customer's data needs, Salesforce Archive empowers businesses to design and automate archiving processes, store vast amounts of historical data, and retrieve it on demand. It utilizes a highly efficient archiving engine, ensuring the Salesforce instance remains fast and responsive even as data grows.

Key Features of Salesforce Archive

Supports Both Standard and Custom Objects

One of Salesforce Archive's standout features is its ability to handle standard and custom objects. This flexibility means the ability to design and implement archiving policies tailored to each customer's unique business needs. Whether you're managing customer records, transaction data, or custom objects explicitly built for your business, Salesforce Archive promises to be a valuable tool.

Automated Archiving Policies

Salesforce Archive allows users to automate their data archival processes. You can set policies that dictate how often archival jobs run, whether daily, weekly, or based on a custom schedule.

Custom Scheduling of Archive Jobs

You get to decide when and how often archive policies should run. You can configure the system to archive inactive data regularly without manual intervention, keeping your active Salesforce environment lean and fast.

Archiving Inactive Records, Files, and Attachments

From outdated records to large files, Salesforce Archive automates the removal of data you no longer actively use. However, it's not deleted—it's stored securely and remains accessible when needed.

Seamless Access via Salesforce Connect

Archived data is kept outside your primary Salesforce instance but can be viewed directly through Salesforce Connect. This means your archived data doesn't occupy storage space but is still accessible whenever needed.

Built-In Compliance and Security

All archived data remains within the Salesforce Trust Boundary, adhering to strict security standards. Making Salesforce Archive a highly secure option for industries dealing with sensitive data or strict regulatory compliance requirements.

Understanding the Storage Architecture

Separate Tech Stack for Performance

Salesforce Archive operates on a separate technology stack within the Salesforce ecosystem. This separation ensures that archived data does not interfere with active system processes, improving query performance.

Security and Compliance within the Salesforce Trust Boundary

Salesforce has designed the archiving solution to meet its rigorous security protocols, ensuring that archived data remains secure and compliant with standards such as GDPR and CCPA.

Automating Your Data Cleanup

Building Custom Archiving Policies

Salesforce Archive lets you define specific archiving policies for your business. Whether dealing with standard or custom objects, you can automate data cleanup based on the frequency and rules that make the most sense for your operations.

Policy Creation for Standard and Custom Objects

Whether working with standard Salesforce objects like Accounts and Contacts or custom objects, Salesforce Archive allows for tailored archiving policies that address your unique data requirements.

Monitoring Archive Jobs and Sessions

The Archive Management UI provides full transparency into archiving jobs, showing policy names, descriptions, job status, and frequency, so you always know what's happening with your data.

Real-World Use Cases for Salesforce Archive

Boosting Query Performance and User Productivity

By offloading inactive data, Salesforce Archive significantly speeds up query response times and dashboard load speeds, helping users stay productive.

Reducing Redundant Records and Data Footprint

By automating the removal of inactive data, Salesforce Archive helps reduce redundancies and ensures a cleaner, more efficient Salesforce environment.

Regulatory Compliance for Data Retention

Whether it's healthcare records or financial transactions, archived data can be kept securely for compliance while remaining accessible when needed.

How Salesforce Archive Improves Compliance

GDPR, CCPA, and Industry-Specific Standards

Salesforce Archive offers a secure and compliant way to retain historical data, helping organizations comply with global data regulations.

Secure Archival of Historical Data

Salesforce's security protocols protect all archived data, ensuring your business complies with privacy regulations while reducing storage costs.

Integrating Salesforce Archive with Other Tools

Salesforce Connect for Data Retrieval

Using Salesforce Connect, you can seamlessly retrieve archived data, giving you full access to historical records without cluttering your active data store.

Extending Archival Capabilities with Salesforce Shield, Backup, and Data Mask

For even greater data control, Salesforce Archive can be integrated with tools like Salesforce Shield for auditing, Salesforce Backup for data recovery, and Data Mask.

Composable Commerce Building Blocks or Building Chaos?

rei.r.joshua@gmail.com (Rei) — Fri, 08 Mar 2024 23:24:50 GMT

The explosive growth of e-commerce forces businesses to constantly re-evaluate their online selling strategies. The siren song of “composable commerce” echoes through the industry, promising unparalleled flexibility and the ability to create the perfect customer experience. Platforms like Salesforce Composable Commerce offer a headless architecture, allowing businesses to cherry-pick “best-of-breed” components and assemble their dream tech stack. Yet, as with many compelling trends, it’s crucial to pierce through the marketing buzz and understand the true costs and complexities before jumping headfirst.

In this article, we’ll delve into Salesforce Composable Commerce and Salesforce Commerce Cloud SFRA. We’ll examine their features and promises, but also cast a critical eye on the challenges often hidden in the fine print.

Key Considerations

The siren song of “composable commerce” might be alluring, but before diving in, it’s crucial to ask yourself some hard questions:

Do you have the development resources for the increased integration needs of a composable approach?
Are you prepared to troubleshoot performance and reliability issues potentially spanning multiple vendors?
Is “ultimate” flexibility crucial, or could a more structured approach provide the right balance for your business?

These questions lie at the heart of the composable commerce dilemma. Let’s dive deeper into the complexities and tradeoffs…

Salesforce Composable Commerce: The Promise and the Pitfalls

Salesforce Composable Commerce adopts a headless commerce architecture, empowering businesses to hand-select individual components (search, content management, payment processing, etc.) and stitch them together using APIs. This approach promises maximum flexibility, customization potential, and freedom from the constraints of a monolithic platform.

The Flexibility Façade: While flexibility is the headline feature, the practicalities of integrating components from different vendors are often messy. Mismatched APIs, conflicting data models, and the sheer complexity of managing multiple dependencies can undercut the promised agility.
The Customization Conundrum: In theory, you can tailor the customer experience to perfection. In reality, creating a cohesive frontend with disparate components requires both architectural vision and a hefty dose of development effort, creating potential for fragmented user journeys.
The Need for Specialized Talent: True composable success often hinges on in-house teams fluent in APIs, microservices, and headless development. Hiring or retraining for this skillset can add significant overhead.

Salesforce Commerce Cloud SFRA: The Safe Harbor

Salesforce Commerce Cloud Storefront Reference Architecture (SFRA) offers a more traditional, structured approach to building e-commerce sites. It provides pre-built templates, best practices, and a focus on mobile-first design, expediting development and ensuring a baseline of industry-standard functionality.

Faster… But How Far?: While SFRA promises faster time-to-market, extreme customization might still involve wrestling with its underlying framework. It’s essential to be realistic about how far you can stretch it based on your unique needs.
Cost Savings… With Caveats: The pre-built nature of SFRA can reduce development costs, but ongoing customization or integration with external systems can still add complexity.
Mobile-First… To a Point: SFRA’s mobile focus is commendable but keep in mind that leading-edge, highly personalized mobile experiences might be easier to achieve with the granular control of a composable architecture.
Salesforce Ecosystem: Blessing or Burden?: SFRA’s connection to Salesforce means regular updates and a degree of stability. However, it also creates a reliance on Salesforce’s development roadmap, and potentially limits your agility when responding to market trends.

Comparing Costs and Maintenance Requirements

When choosing between Salesforce Composable Commerce and SFRA, a careful analysis of both upfront costs and ongoing maintenance requirements is essential.

Initial Setup Costs:

Composable Commerce: Often has higher initial setup costs due to the need to select, integrate, and configure multiple components. Expertise in API management and integration may be required.
SFRA: While a less complex architecture, SFRA projects still involve development and customization, though this may be less extensive compared to Composable Commerce.

Ongoing Maintenance:

Composable Commerce: Can demand more continuous maintenance as updates and version changes from multiple component providers need management. May require a specialized team with headless architecture experience.
SFRA: May have more predictable maintenance patterns due to a centralized update flow from Salesforce. However, some level of ongoing development is usually required for updates and new feature implementation.

Solution Architecture Complexity

The complexity of your solution architecture has significant implications for your team, costs, and agility. Let’s dissect the differences between the two Salesforce approaches:

Salesforce Composable Commerce:

Greater Complexity: Due to its decentralized, component-based nature, Composable Commerce typically has a higher level of complexity.
Integration Expertise: Meticulous integration of various components is crucial for seamless functionality, potentially requiring specialized skills in APIs and microservices.
Potentially Streamlined Workflows: With the right expertise, the modular nature of Composable Commerce can enable highly efficient development workflows, where updates can be made independently to individual components.

Salesforce Commerce Cloud SFRA:

Moderate Complexity: SFRA follows a more traditional architecture with fewer moving parts. It balances flexibility with a degree of standardization.
Customization Within Limits: Customization is possible within SFRA, but fundamental architectural changes can be more challenging than with a fully composable approach.

Conclusion and Recommendations

The choice between Salesforce Composable Commerce and Salesforce Commerce Cloud SFRA ultimately comes down to your specific business needs, resources, and long-term goals.

Composable Commerce is ideal for:

Larger enterprises with dedicated development teams experienced in headless architectures.
Businesses prioritizing maximum flexibility, customization, and the ability to rapidly adopt new technologies.
Companies ready to accept potentially higher initial setup costs for the long-term benefits of agility.

SFRA is a strong fit for:

Companies seeking a robust, proven solution with faster time-to-market.
Businesses that prefer to leverage Salesforce’s core expertise and continuous development roadmap.
Organizations that may have less in-house developer expertise in modern frontend technologies or complex integrations.

Composable Commerce: A Cautionary Tale (with Exceptions)

Composable commerce promises freedom and flexibility, enticing businesses to hand-pick technologies for the ultimate customer experience. Yet, this “best-of-breed” approach often obscures a sobering reality — one of complexity and hidden costs.

For large enterprises with robust in-house development teams fluent in headless architectures and API-driven systems, composable commerce can be a powerful tool for customization rapid innovation.

However, its marketing often downplays the burdens it places on businesses, especially those without significant development resources:

The Integration Illusion: The idea of seamless integration is often a mirage. Mismatched APIs can lead to costly integration headaches, negating promised time-to-market gains.
The Maintenance Nightmare: Managing a patchwork of components from multiple vendors becomes a logistical nightmare, diverting resources from innovation.
The Expertise Gap: Composable commerce demands specialized skills in APIs, headless architectures, and distributed systems. This skillset is often scarce and expensive.
Performance Anxiety: A slow-loading component or a poorly designed API call can cripple the entire shopping journey. Performance optimization becomes a constant concern.

Composable commerce often means trading one type of rigidity (monolithic platforms) for another (complex integrations and constant updates). Businesses seeking “ultimate flexibility” may find themselves feeling trapped in a web of technical debt and operational overhead.

The Imposter In You Is A Strength Not A Weakness

rei.r.joshua@gmail.com (Rei) — Mon, 04 Mar 2024 02:37:53 GMT

Do You Ever Feel Like a Fraud?

Despite your credentials, do you doubt whether you truly deserve your position?

Do you chalk up accomplishments to luck no matter how hard you worked?

Does praise make you uncomfortable rather than proud?

Are you often anxious about being “exposed” as less competent than people think?

If you answered yes, you likely struggle with imposter syndrome. The persistent feeling of being an intellectual fraud despite evidence of your competence and achievements.

Rather than accept proof of their talents, people suffering from imposter syndrome feel like phonies who slipped through the cracks. They dismiss external validation and have intense self-doubt. High achievers struggling with perfectionism and self-perception issues often have imposter syndrome.

Origins of Self-Doubt

Few of us escape childhood without absorbing society’s impossible standards. Images of flawless superstars and airbrushed celeberity's fuse expectations of perfection we carry into adulthood. We often inherit a deep seeded sense of not measuring up.

Thus the origins of doubt take root. Our inner critic emerges who constantly moves the finish line of success further away. Once we cross one pinnacle, it compels us towards the next. It allows no pause for satisfaction or reflection before demanding more.

In this exhausting quest for validation, we over-identify self-worth with professional achievements. Unconsciously we hope the next promotion will finally still our inner judge. Yet more achievements only cause a short lived quieting of the critic insisting we do not deserve what we have worked so hard to achieve.

Each accomplishment gets discounted as luck no matter how strategically earned. We attribute promotions to being in the right place at the right time rather than acknowledging our talents. Praise rings hollow, invoking that childhood feeling we do not quite belong with the so-called best and brightest.

The roots of self-doubt run deep. But awareness of their origins helps us reflect on the unachieveable and flawed nature of these expectations. We can then reframe accomplishments as hard-won through skill, dedication and pervasiveness. Quieting your inner critic is a lifelong journey, but each small win speaks to the strength in herit in each of us.

Quieting Inner Voices

The most insidious aspect of self-doubt is how it isolates us. It whispers in our ear that admitting uncertainty or seeking assistance will expose our perceived ineptitude or weakness. So we refrain from sharing our day to day challanges with peers that might benefit from our solidarity.

Yet community and connection are the strongest medicine for imposter syndrome. We can begin by celebrating small wins that our inner critic tries to diminish. Did we volunteer for a project that showcases abilities? Or finish a task in less time than expected? Quieting self-doubt involves writing down and reflecting on accomplishments big and small and recognizing them for what they are… Wins.

We can also soothe ourselves with the same support we would extend to a friend in our shoes. Talk to yourself as you would a peer working to balance high expectations at work with mental health. Check in on emotional needs and make sure you feel supported rather than scolded.

Finally, remember the communities alongside you. Seek mentorship from leaders who appreciate candor about self-doubt. Build bonds with those who nurture growth by sharing their own lessons learned. And pay it forward by mentoring newcomers transitioning into first careers or still growing into their own.

In stillness we can hear, beneath our skin, the low hum of inner strength waiting to be realized. Internal critics lose their power when we redirect focus to wins, self-care, and communal collaboration. For in this we realize excellence stems not from solo perfectionism but from community.

Hidden Strengths

Imposter syndrome distorts our self-perception by obscuring our slumbering strengths. The drive fueling extra hours at the office stems from dedication, not deficiency. We wish to serve customers well, so we lose sleep perfecting our work. Perfectionism shows we care about excellence.

Behind the feeling of fraudulence lies sincerity, not indifference. We fear being revealed as incompetent because we are driven so deeply to contribute our talents and support our team and peers. Self-doubt plagues the committed, not the indifferent. It is the passion to develop skills and do well that keeps us up at night.

Our fixation on flaws eclipses quiet virtues others likely admire. The courage to admit uncertainty when tackling novel tasks. Empathy in mentoring newcomers rather than hoarding knowledge. Curiosity to experiment with innovative solutions. These admirable traits emerge when self-criticism fades.

Rather than demand perfection, identify latent strengths. Answer inner voices undermining you by recognizing the virtues that fuel your dedication — care for people, devotion to craft, willingness to better yourself. Then channel that energy into meaningful work rather than seeking validation. Stay immersed in tasks that align to your purpose. Funnily enough, this mindset that ignores accolades often earns them and with them respect.

Words to Live By

I know imposter syndrome can be loud with doubts like “You don’t deserve this job.” But hear this: those fears arise because you care deeply. Self-doubt plagues the sincere, not the indifferent.

You lose sleep worrying over work because you aim to serve customers well. You drill skills because you value self-betterment. Though imposter feelings may paralyze, your dedication shows a hidden strength — caring that drives excellence.

Rather than demand perfection, celebrate small wins. Answer cruel inner voices with encouragement. Know you’re not alone in this feeling. Together we can transform self-doubt into self-discovery.

Going forward, take small steps to build confidence. Sharpen skills through quick tutorials. Chip away with self-compassion. Your dedication shows potential for purpose and impact.

Refocus this feeling fueling your sleepless nights — let it drive meaningful work instead. Remember your wish for excellence comes from a heart that wants to contribute, that compassion is a quiet strength ready to shine.

Rust The Future Proof Systems Language

rei.r.joshua@gmail.com (Rei) — Sun, 03 Mar 2024 02:40:56 GMT

Industry Embrace of Rust

Rust has gained credibility across the tech industry thanks to its performance, safety and scaleability:

Cloud Giants like AWS, Azure, Cloudflare and Fastly use Rust for cloud services and edge computing.

Tools & Databases like npm, MongoDB, Vector and Databend leverage Rust’s speed and memory safety.

Operating Systems from Linux to Windows to Fuchsia incorporate Rust for reliability.

Web Tech sees Rust drive Firefox, Deno, CDNs, APIs and more.

Blockchains like Solana, Polkadot and Ethereum rely on Rust for their core infrastructure.

With Rust being battle-tested across domains from tiny devices to massive cloud platforms, it seems primed for long-term industry adoption driven by its unique capabilities.

Over the past decade, an exciting systems programming language called Rust has rapidly gained adoption across the industry. Originally created by Mozilla and now stewarded by the Rust Foundation, it has quickly become one of the fastest growing and most beloved languages after finally breaking through to the mainstream in recent years.

Despite being over 10 years old, Rust was mostly an academic curiosity and niche language for its first decade. But it now appears to be hitting an inflection point and coming into its own. Surveys show it topping charts as the “most loved language” among developers for years running.

Leading technology companies have started leveraging Rust for key infrastructure, products, and services. But what explains this once niche language’s newfound mass adoption and meteoric rise to prominence? Much of Rust’s success stems from how it creatively tackles long-standing pain points in systems programming.

Specifically, Rust guarantees memory safety without requiring a garbage collector for memory management. It does this via new concepts like ownership and borrowing that statically enforce validity of memory references at compile time. This eliminates entire categories of crashes, vulnerabilities, and bugs that have plagued systems programmers for decades — all without runtime overhead.

In this article, we will explore Rust’s unique approach to memory safety and other key features that make it well suited for performance-critical systems software like operating system components, embedded devices, browsers, and more. We’ll cover concepts of ownership, borrowing, and lifetimes that come together to enable Rust’s guarantees.

Memory Safety Without the Garbage Truck

Rust’s novel concept of ownership establishes clear resource management rules that the compiler rigorously enforces. Each value in Rust has a variable that serves as its unique owner. Ownership confers both responsibilities and privileges:

There can only be one owner at a time
The owner has exclusive access to modify or move the resource
When the owner goes out of scope, the resource is automatically cleaned up

Concurrency Fearless by Default

A key innovation in Rust is the concept of borrowing. Borrowing allows access to data that is owned by someone else in a controlled manner. When a variable is borrowed, it creates a temporary reference to the resource that enforces rules about valid access at compile time.

Borrowing in Rust comes in two flavors immutable and mutable borrows. Immutable borrows use the & operator. These allow read access to the data, but prevent modifying it as long as the borrow exists:

Zero Bugs and Zero Cost How is This Possible?

Lifetimes represent the scope for which references in Rust are valid. Each reference has an associated lifetime that ensures it always points to valid, allocated data.

For example, consider a function that returns a reference to data created inside the function:

Rust is a Breath of Fresh Air

So by now you see why Rust is such a big deal. It gives you both safety and speed — without the usual tradeoffs. Rust sidesteps entire classes of major headaches that have plagued programmers for ages.

Now it won’t click overnight. That borrow checker enforces unique rules; expect a learning curve as you adapt. But developers who embrace Rust tend to become hooked. The superpowers are just too good. Leaders like Microsoft, Google and AWS are betting big on Rust too. They want what it brings — secure, high-performance code. And Rust’s ecosystem expands daily. Rust may never become as popular as Java. But not every tool needs to do everything. Rust solves nasty problems in computing at the lowest level. It makes programmers happy along the way. So while it may never be used everywhere, Rust punches way above its weight class. And working with it just might rekindle that coding joy and thrill that drew you to programming originally. That alone makes Rust worth mastering.

By statically tracking resource ownership as variables enter and exit scope, Rust ensures resources are managed safely and efficiently without requiring manual allocation/freeing or garbage collection.

The owner of a resource is responsible for both its usage while in scope as well as clean up when no longer needed. This simple but strict rule eliminates entire classes of bugs.

We’ll build on ownership through language mechanisms like borrowing and lifetimes that enable sharing references to resources in well-defined ways. But ownership establishes the foundation.

The Rust compiler (known affectionately as “the borrow checker”) ensures these borrowing rules are satisfied. This prevents invalid references and ensures memory safety without any runtime costs.

Next we’ll explore Rust’s concept of lifetimes, which represent the scope for which borrows are valid…

Mutable borrows use the &mut operator. These allow both reading and modifying the data, but can only have one active mutable borrow at a time:

This code does not compile in Rust because the String s is deallocated once the function exits. So the returned reference would be invalid.

To fix this, we need to associate the lifetime of the reference with the lifetime of s. Rust allows specifying lifetime parameters to represent these scopes:

Now the returned reference is only valid for the lifetime 'a, which matches the scope of s. This makes the code safe.

Lifetime analysis is performed at compile time by Rust to catch any invalid references before they cause issues at runtime. They help guarantee memory safety without any runtime cost.

Lifetimes are usually implicit and inferred automatically in Rust. But understanding how explicit lifetimes work unlocks the full power and flexibility of Rust’s borrow checker for advanced scenarios.

Sales Cloud Lifecycle Transforming Leads into Revenue

rei.r.joshua@gmail.com (Rei) — Sat, 24 Feb 2024 19:28:13 GMT

Salesforce Sales Cloud stands at the forefront of CRM solutions, offering businesses a comprehensive platform to enhance their sales operations. It streamlines the sales process, ensuring that potential leads are not only captured but also effectively converted into profitable relationships. By providing a detailed overview of each stage in the sales lifecycle, Sales Cloud helps businesses manage their sales funnel with precision.

Capture Initial Lead Data

The journey begins with the Lead object, designed to capture and track potential leads. At this initial stage, businesses gather numerous pieces of information about prospective prospects, laying the groundwork for an effective follow-up strategry to convert these leads into an opportunity.

Conversion of Leads

The lead conversion process marks a the transition where leads are converted into three key objects: Account , Contact , and Opportunity . This phase is pivotal as it signifies the potential lead’s interest in becoming a customer, turning data into actionable sales opportunities.

Account Object: Represents the customer’s company or organization, serving as a repository for all interactions and transactions.

Contact Object: Personifies the individual customer contacts within a given customer Account, ensuring personalized communication and relationship building.

Opportunity Object: Manages potential sales and deals, providing a snapshot of the possible revenue and enabling sales teams to prioritize their efforts into keystone accounts.

Tracking Opportunity Progress

Sales Cloud enables tracking the progression of opportunities through various stages, such as qualification , negotiation , and closure . This visibility ensures that sales teams can strategically allocate their resources and efforts where they will have maximum effect.

Qualification: This stage is all about identifying potential opportunities that align with your business capabilities and customer needs. It’s a critical filter to ensure that sales efforts are focused on leads with genuine potential for conversion, optimizing resource allocation right from the start.

Negotiation: At this juncture, the dance of give-and-take occurs, where pricing, terms, and conditions are discussed in detail. It’s a pivotal phase where sales teams leverage their skills and tools to shape the offer in a way that meets both parties’ expectations, inching closer to a win-win outcome.

Closure: The final leap where agreements are signed and deals are sealed. This stage represents the culmination of the sales process, where meticulous efforts are rewarded with a successful transaction. It’s a moment of validation for the strategies employed, setting the stage for future opportunities and fostering long-term relationships.Product Interest

Quote Generation ( Optional )

Integrating the Quote object into the Sales Cloud lifecycle streamlines the transition from understanding customer needs to creating precise, customized proposals. By using the Quote object, sales teams can generate detailed quotes based on the specific products and services a customer is interested in, ensuring the proposal aligns with their requirements. This step not only personalizes the sales experience but also formalizes the offer, making it a crucial component in moving towards deal closure. The ability to create and adjust quotes easily allows for clear communication and negotiation, facilitating a smoother path to sales success.

Product Catalog and Pricing

The Product2 object, along with PriceBook and PriceBookEntry objects, manage the catalog items and their pricing strategies. This ensures that sales teams can offer competitive and accurate pricing for products and services.

Order Creation and Fulfillment

Upon successfully closing a deal, the Order object comes into play, transitioning from sales to fulfillment. It captures the essence of the customer’s purchase, detailing the products involved through the OrderItem object which in turn associates with a specific Product2 object.

Salesforce Order Management (Optional)

Salesforce Order Management represents an advanced option for businesses aiming to elevate their operational capabilities beyond the foundational offerings. Integrating Salesforce Order Management with Sales Cloud facilitates a comprehensive solution that spans the entire process from lead acquisition to fulfillment. This integration provides businesses with enhanced control and granularity over the order fulfillment process. Additionally, Salesforce Order Management introduces a variety of improvements, including streamlined operations, improved customer service capabilities, and better inventory management. By leveraging these enhancements, businesses can achieve a more efficient, transparent, and customer-focused fulfillment process, thereby ensuring that every step from the initial lead to the final delivery is managed with precision and care. This holistic approach not only optimizes operational efficiency but also significantly enhances customer satisfaction, positioning businesses for greater success in a competitive marketplace.

In Closing

The Salesforce Sales Cloud lifecycle offers a holistic view of the sales process, from lead capture to order fulfillment. By leveraging the interconnected Salesforce objects, businesses can ensure a seamless transition between each stage, enhancing their sales efficiency and customer relationships. Understanding this lifecycle is crucial for businesses looking to optimize their sales operations and drive growth through strategic sales management.

What is Tableau and How Can it Help Supercharge Salesforce Data

rei.r.joshua@gmail.com (Rei) — Wed, 21 Feb 2024 19:42:44 GMT

Salesforce is essential for capturing valuable customer and operational data, crucial for smart decision-making in today’s competitive business environment. While standard reports provide basic summaries and insights, truly understanding the complex dynamics behind trends and identifying new opportunities requires more advanced analytics. This is where standard tools often fall short.

Tableau steps in to fill this gap, offering a powerful way to explore and understand Salesforce data beyond the basics. With Tableau, you can quickly see how sales are doing across different regions, find out which products are boosting your profits, or identify where customers are dropping off. This goes beyond creating simple charts; it’s about turning your data into actionable insights that can influence strategic decisions and drive business growth.

Tableau and it’s Journey to Prominence

Tableau’s journey from a startup to a prominent player in the data visualization and business intelligence industry is a testament to its innovative approach and commitment to making data understandable to everyone.

Here’s a brief history of Tableau:

Founding and Early Years

2003: Tableau was founded by Chris Stolte, Christian Chabot, and Pat Hanrahan. The foundation of Tableau was laid at Stanford University, where Stolte was working on a PhD project under the guidance of Hanrahan, a professor. Their project focused on visualization techniques for exploring and analyzing relational databases, which led to the development of VizQL (Visual Query Language), the core technology behind Tableau’s products.

2004: Tableau launched its first product, Tableau Desktop, which allowed users to create interactive data visualizations without any programming skills.

Growth and Expansion Era

2006–2010: Tableau introduced Tableau Server, enabling organizations to share and collaborate on data visualizations and reports online. This marked a period of significant growth for Tableau, as it expanded its product line and started to gain traction among businesses looking for user-friendly data analysis tools.

2013: Tableau went public with an IPO on the New York Stock Exchange under the ticker symbol “DATA.” The IPO was a success, reflecting the market’s confidence in Tableau’s potential and its role in the expanding data visualization market.

Innovation Drives Industry Recognition

Tableau has continued to innovate, adding new features and capabilities to its platform, including data preparation tools, mobile access, and advancements in artificial intelligence and machine learning through integrations and enhancements. Its commitment to making data analysis accessible and engaging has contributed to its widespread adoption across many industries.

Growth through Strategic Partnerships and Acqisitions

Tableau has continued to expanded its capabilities and market reach through a methodalgy of strategic acquisitions and partnerships. Notable acquisitions include HyPer, a high-performance database system, and ClearGraph, a startup specializing in natural language query technology, this has allowed Tableau to continue innovating and enhancing there analytics capabilities.

Acquisition by Salesforce

2019: In a move that marked a significant milestone in Tableau’s history, Salesforce acquired Tableau for approximately $15.7 billion. This acquisition integrated Tableau’s advanced analytics capabilities with Salesforce’s leading CRM platform, aiming to create the most powerful analytics platform for businesses.

Salesforce Empowered Growth and Development

Under the Salesforce umbrella, Tableau has continued to grow and evolve, expanding its reach and deepening its capabilities in data visualization and business intelligence. It remains a key player in the industry, known for its powerful, user-friendly analytics platform that serves millions of users worldwide.

Technical Advantages for the Salesforce Ecosystem

Tableau’s acquisition by Salesforce has bolstered its reputation as a leading analytics platform for enterprise data. Its native integration with Salesforce’s enterprise-class CRM software directly enhances the value of your existing Salesforce investment. Let’s explore how these two products combine to create a powerful analytics duo.

Intuitive Use of Salesforce Data: Seamless connection to Salesforce objects (custom and standard) lets you visualize the data without complex workarounds. If you understand how your Salesforce is structured, Tableau will mirror that for easy analysis.
Respecting Your Rules: No worries about unauthorized data exposure. Tableau can inherit the roles, permissions, and visibility control you’ve defined within Salesforce. This simplifies user setup and eliminates the risk of accidental data disclosure as your visual dashboards gain broader audiences.
Beyond Salesforce Silos: Tableau goes beyond just what lives within Salesforce. Imagine enriching your analytics by connecting to external marketing data, e-commerce website behavior, or demographic datasets directly mapped to territories. Suddenly, you gain that ‘full picture’ to identify unseen drivers.
Data Handling: Tableau Prep empowers those familiar with visual manipulation tools to curate and reshape data for even stronger visualizations. Tableau partners well within your overall system to give you the perfect output to visualize, explore, and act upon.

Supercharge Your Salesforce Data

Tableau seamlessly complements the strengths of Salesforce, elevating its capabilities beyond those offered by its native reports. This flexible visual analytics platform is designed to unlock deeper insights from Salesforce data, enabling intuitive exploration through:

Powerful Visualizations: Create visually captivating charts, graphs, maps, and more, transforming data from cryptic tables into easily interpretable representations.
User-Driven Discovery: Intuitive filters, drill-downs, and dynamic dashboards encourage iterative analysis, enabling users to self-serve and find unique answers within their data.

Shareable Insights: Communicate patterns and actionable findings through visually engaging dashboards. These become collaborative tools fostering data-driven decision-making across teams.

Tableau Use Cases: From Insight to Action

Tableau brings compelling solutions for scenarios where standard Salesforce reporting feels limiting. Here’s how it unlocks strategic decisions based on deeper, visual insights:

Case Study 1: Mastering Order Analytics

Problem: While Salesforce Order Management serves as the system of record, analyzing intricate patterns across sales figures, product performance, and fulfillment cycles often demands tools beyond what Salesforce native reports can provide.
Tableau Solution: Visualizations reveal critical insights such as: Product mix driving sales (or losses) by region to fine-tune inventory and sales strategy. Revenue distribution across territories to pinpoint growth or underperforming markets. Performance bottlenecks within fulfillment workflows, with visual data on average open days.
Impact: Data-driven decision-making becomes accessible to key stakeholders. Armed with timely insights, teams react proactively to changing trends and can make strategic choices.

Case Study 2: Optimizing the e-Commerce Experience

Problem: e-Commerce platforms like Salesforce Commerce Cloud generate a wealth of data on customer behavior. But uncovering patterns that directly impact conversions and revenue can be complex with tabular analyses.
Tableau Solution: Powerful visualizations can: Map customer journeys from the acquisition source to the checkout (or point of abandonment) to pinpoint optimization opportunities. Spotlight top-performing products and categories by visually associating with revenue trends for tailored promotions or merchandising decisions. Connect shopping cart abandonment patterns with demographic or other data for personalization in retargeting and re-engagement efforts.
Impact: Tableau turns vast e-commerce data into actionable intel. Optimized marketing campaigns, improved product visibility, and frictionless checkout processes elevate the online shopping experience and propel sales growth.

Deployment & Governance Considerations

Successfully integrating Tableau into your Salesforce ecosystem requires a strategic approach with many things to consider:

Tableau Architecture

Cloud vs. On-Premise: Evaluate Tableau Online for seamless SaaS integration or choose Tableau Server for granular control (if hosted within your IT infrastructure). Considerations include user volume, security requirements, and existing system architecture.
Scaling: Anticipate data growth and user adoption. Plan for data extract schedules, server resources, and licensing accordingly for performance and accessibility.
Align with Salesforce: Adhere to user roles and permissions established in Salesforce. Tableau’s robust security model facilitates seamless integration and prevents unauthorized data access.
Data Sensitivity: Consider creating curated data extracts tailored to specific business needs to manage data exposure. Row-level security can refine what each user group sees within a dataset.

Data Freshness & Management

Refresh Strategies: Balance near real-time updates against system load. Explore incremental data refreshes and efficient extract processes provided by Tableau to handle large datasets.
Version Control: Implement structured approaches for versioning Tableau workbooks and datasets, particularly within complex analytic scenarios.

Change Management & Training

Rollout Approach: Consider pilot programs, targeted training, and open communication across business and technical teams to minimize adoption disruption.
Continuous Education: Provide ongoing resources such as tutorials, documentation, and internal communities to promote continuous skill development on the Tableau platform.

Final Considerations & Next Steps

Harnessing the power of Tableau elevates your Salesforce data strategy. Integrating these analytics capabilities is an empowering step for businesses looking to utilize data-driven insights throughout their organizations. To take that first step and continue to expand your knowledge on this cutting edge product:

Hands-On Exploration:

Tableau Trial: Dive in with a free trial to experiment with Tableau’s interface, connect to Salesforce data, and build dashboards relevant to your use cases.
Technical Resources: Delve into developer resources through Trailhead modules, the Tableau API knowledge base, and the Salesforce Developers portal.
Targeted Solutions: Start with a well-defined business problem where Tableau has a transformative potential (refer back to our case studies for ideas). Project success includes creating compelling visual analytics and engaging key stakeholders throughout the process.
Cross-Team Approach: Involve business leaders, and data analyst’s alongside technical professionals and creare shared ownership of new approaches to analytics. Early, positive results build support for the platform expansion.

Continuous Learning

Feature Updates: Stay informed about evolving Tableau capabilities and how the Salesforce partnership influences enhancements like new connections or functionalities.
Data-Driven Leadership: Demonstrate how insightful, visual analytics influence strategic choices. Architects embracing this philosophy lead the development of a more empowered and data-informed organization.

Embracing Tableau can unlock the potential of your Salesforce data, and empower users at all levels to unlock, and enables actionable, business-driving insights.

Salesforce Solution Design Customer Event Stream Integration

rei.r.joshua@gmail.com (Rei) — Sun, 18 Feb 2024 03:17:42 GMT

We have a client who has engaged with us to solve for an outside integration which has limited ability to adpat to their needs. The goal is to make the best of the data they are able to provide and streamline and optimize form the Salesforce side of the fence.

This outside integrator provides a stream of events, these events represent customer data interactions from brick and mortar locations. The exact how on the store side is not relevant to this integration. The following events can be expected to come through the eventstream:

customer.entered.store
customer.shopping
customer.checked.out
customer.exited.store

These events will only ever be passed for customers who have registered an in store account. The goal is to utilize these events to reflect a live representation of a customer journey in store. This data will be utilized to identify sales patterns such as frequency, brands, TIS (Time In Store) etc.

Phase One: Integration Assessment

The first step in any successful integration is asking the right questions to gather as much information as possible. Having detailed information up front is invaluable in our ability to create the optimal solution for the given integration.

Question One:

Does this third party provide a method to send these events in batches or are they only able to send a single event per request?

Answer One:

There is currently no process to send batch events in a single request. Each request contains a single customer event with only information relevant to that event.

Conclusion:

This simple question and answer provides an immense amount of value to the solution we will end up designing. We now know that any bulkification optimizations will have to be made within Salesforce.

Question Two:

What information is provided within each event payload. Do the various event payloads conform to a standerdized pattern or does each event contains unqiue data? Can an example of each event payload be provided up front to model against?

Answer Two:

The event payload structure is standardized with some unique data points specific to the checked out event which provides details on the products purchased during checkout.

Find a sample of each event payload below.

Conclusion:

We now have examples of each possible payload that will pass into Salesforce via this integration. We know the overall payload structure is standerdized. A JSON object containing a series of key value pairs with the following keys always present:

id: a unique event id
name: the event name one of the four outlined events
timestamp: the date/time the event took place
customer_id: an id represneting the customer that the event is associated with

We should also take note that the customer.checked.out and customer.exited.store events have additional keys associated with them. These contain additional data relevant to the given event type:

items: contains an array of objects each object represents an item that was purchased during checkout. Each item provides data such as the product id, name, pricing and promotions.
time_elapsed: provides the time a customer has spent within the store from the time they enter to the time they exit.

Question Three:

Can the integration partner garuntee the sequence of events for a given customer? Is there a possability of events coming over out of order?

Answer Three:

The order of events is managed on the integeration side each event must be sent successfuly before the next event in the sequence will be sent. While not common it is possible in rare cases that a duplicate event sequence is transmitted which could cause duplicate data to be presented in the stream.

Conclusion:

So we don’t have to worry about controlling the sequence of events on the Salesforce side. However we did learn that there is a fringe case of duplicate event streams being sent over which we will probably want to plan for in our final solution.

Question Four:

Given a scenario where an event fails to be ingested by Salesforce is it possible for us to provide some kind of response back to the integration to indicate this failure and cause? Does the integration have a retry mechanism in place for when this situation occurs?

Answer Four:

The Salesforce endpoint should respond with a 500 status code indicating a failure the error message is not specifically utilized by the integration but the 500 will push this event into a queue for retry attempt.

Conclusion:

This is answer gives us the response required to trigger the integrators built in retry mechanism and based on our previous question we know that events will only ever be pushed in sequence meanaing if an event is put into the retry queue events that would follow will not be processed until the retry has completed successfully.

Phase Two: Solution Design

How will data get into Salesforce?

Implementing a REST endpoint in Apex, paired with a Connected App, offers a secure, scalable way for external integrations to authenticate and feed data into Salesforce. This setup not only ensures data is efficiently ingested but also leverages Salesforce’s robust security model. Through Connected Apps, external services can authenticate using OAuth, providing a secure method to access Salesforce data, and the Apex REST endpoint allows for tailored processing of incoming data, optimizing how it’s handled within the Salesforce environment.

How can we optimize and bulkify?

When handling single incoming event payloads, directly updating Salesforce records for each can strain system resources. This approach, while manageable transaction-wise, can lead to performance degradation due to the increased load on Salesforce’s database, potentially slowing down operations system-wide. It also heightens the risk of record locking conflicts, where simultaneous updates to the same record or related records can block one another, leading to processing delays. Optimizing how these events are managed within Salesforce is crucial to maintain efficiency and ensure smooth operation, especially under high volumes.

Because the integrator does not provide a means to ingest bulk events we’ll need do our best to optimize as much as possible on the Salesforce side as the events enter the system.

So as was mentioned earlier updating Account records directly as the events come in is not an effective solution. So what we are going to do is generate a custom object for each event. This reduces the workload of the incoming request process to just creating a new object representing this event within Salesforce because each of these custom objects is unique there is no risk of record locking or other concerns we mentioned earlier. We’ll call our new object Customer_Store_Event__c this object will have the following fields:

Standard Fields

Name: String: which will match the event names from the payload

Custom Fields

CustomerId: String: stores event event customer id
TimeStamp: DateTime: stores the event timestamp
EventId: String: store the unique event id
CheckoutItems: LongText: Stores the raw items Array in the case of a checkout event
ShoppingTimeElapsed: DateTime: the elapsed shopping time provided in th case of a store exit event

How do we deal with fringe duplication possibility?

So now that we have an effective pattern to ingest these events and store them in Salesforce for future bulk processing we want to remember to account for the possibility of duplicate events. Remember this detail was revealed to us in the answert to question three as a possible situation in some rare cases. Luckily this is simple enough to accomplish in our REST endpoint. We know that we have a unqiue event id provided on each payload and the event id is stored on our newly created custom objects. So with a simple query we can effectively filter out incoming events that match an existing event id within Salesforce

What is our primary processing mechanism

Now that we have these custom objects and they contain our customer in store event data we have a couple different questions we need to answer related to processing and utilizing this data.

By what means do we want to process these objects?

To optimize the processing of customer event data, our solution will leverages Queueable and Schedulable Apex. This method was selected over batch jobs or other options for its enhanced control over execution, allowing for dynamic adjustment to processing loads and the ability to chain jobs for complex workflows. This strategic choice ensures efficient data handling, maintaining system performance, and providing timely customer behavior insights.

At what interval do we need to process these event objects?

This process will run every 10 minutes in an attempt to balance near real time data representation in Salesforce with effective usage of asynchronous resources. Once the solution has been tested further we can tweak this cadance as needed based on traffic and available resources.

Where is this data being processed to?

With this event data being tied to registered in store customers the logical location for these details to be stored is on the associated Account object. To accomplish this we’ll need to make sure that the external customer ids are present in Salesforce if these ids are not available at the Account level in Salesforce already then we will need to work with the client to import these into Salesforce. For the purpose of this example our client has alrwady maintained these ids on the Account object in a custom filed called In_Store_Customer_Id__c. Now as process these events in our queuable context we can easily query for the matching customer Account

The previous code example is not fully flushed out and makes some assumptions for the puproses of this article I am representing enough to present the high level details.

Phase Three: Solution Review

After implementing the REST endpoint in Apex and setting up our custom object, Customer_Store_Event__c, to capture the stream of events from the integration partner, it’s time to reflect on the efficacy of our solution and its alignment with the project’s goals.

Key Takeaways from Implementation:

Efficient Data Ingestion: Our approach to creating a custom object for each event has streamlined the process of data ingestion into Salesforce. This method has effectively bypassed potential bottlenecks associated with direct updates to Account records, demonstrating a high degree of efficiency in handling incoming data.

Optimization and Bulkification: By leveraging Queueable and Schedulable Apex for processing the custom event objects, we’ve introduced a scalable solution that adjusts to processing loads dynamically. This choice has proven crucial in maintaining system performance while ensuring data is processed and utilized effectively.

Fringe Duplication Handling: The strategy to query for existing event IDs before processing new events has effectively mitigated the risk of duplicating data due to the integration partner’s rare sequence duplications. This preventive measure has preserved the integrity of our data, ensuring that our Salesforce environment reflects accurate customer interactions.

Data Processing to Account Records: The logical step of associating event data with customer Account records based on in-store customer IDs has laid the groundwork for insightful analytics on customer behavior. This connection not only enriches customer profiles but also opens avenues for advanced analysis and personalized engagement strategies.

Areas for Further Review and Adjustment:

Processing Interval Evaluation: While the decision to process event objects every 10 minutes strikes a balance between real-time data representation and resource optimization, ongoing monitoring is essential. Adjustments may be necessary as we gather more data on system load and event volume fluctuations.

Data Representation and Utilization: The ultimate success of this integration hinges on how the processed data informs business strategies and customer engagement. Further review is needed to ensure that the insights derived from the event data are actionable and align with the client’s objectives. This includes evaluating the dashboard and reporting mechanisms in place to surface these insights.

Handling Data Processing Issues: As we take ownership of the data from the event stream, developing a robust mechanism to handle processing errors becomes paramount. This includes setting up alerts for failed processing attempts and creating a clear workflow for addressing these issues to minimize impact on data quality and availability.

Final Thoughts:

Our journey to integrate and utilize the event stream from the client’s brick-and-mortar locations into Salesforce has been both challenging and enlightening. As we move into the final review phase, it’s crucial to engage with the client for feedback, assess the system’s performance under real-world conditions, and remain flexible to iterate on our solution. The goal has always been to not just capture data but to transform it into meaningful, actionable insights that empower our client to make informed decisions and enhance the customer experience.

By maintaining a focus on scalability, data integrity, and actionable analytics, we are well on our way to realizing the transformative potential of this Salesforce integration, setting a new standard for customer journey analysis in physical retail spaces.

Looking Ahead:

The success of this project will be measured not just by the technical robustness of our solution but by its impact on the client’s business. As we refine our approach and continue to innovate, the lessons learned here will undoubtedly inform future integrations, underscoring our commitment to delivering solutions that not only meet but exceed a clients’ expectations.