Daniel McGhan

Nothing breaks at first. It just gets expensive. Duplicate staffing. Residual access. Distorted reporting. Here’s how high-growth firms scale revenue without losing control.

2

In this live stream, Developer Advocate Alex Martinez tests out the MuleSoft MCP (Model Context Protocol) Server—from installation to hands-on demos—to explore how it can generate, run, and modify Mule applications using natural language.

36

18 Comments

Salesforce Tip of the Day – Lightning Out Use Lightning Out to embed your Lightning Components in external web applications — perfect when you want Salesforce functionality outside the platform. ✅ Allows you to render Lightning components on non-Salesforce pages. ✅ Great for customer or partner portals that aren’t on Experience Cloud. ✅ Uses your Salesforce org as the component host and authentication source. Example setup: 1. Add the Lightning Out dependency in your Visualforce or external page: HTML <​script src="https://lnkd.in/dcD5JP5a"><​/script> 2 Bootstrap your Lightning app HTML <​script> $Lightning.use("c:MyApp", function() { $Lightning.createComponent("c:MyComponent", {}, "lightningContainer"); }); <​/script> Tip: Make sure CORS and Lightning Out dependencies are properly configured in Setup → CORS and Lightning Out Dependencies.

1

Salesforce Story: Safely Decommissioning Unused Fields Worked on a Salesforce story to identify and decommission unused custom fields in a high-volume, long-running org. Even though the fields showed zero data usage over multiple years, they were still referenced across: Apex controllers and batch logic Report types and reports Permission sets and profiles Related lists and layout metadata Rule-engine configuration (JSON-based metadata) CI/CD destructive deployment steps The work involved: Validating data usage without full table scans Refactoring Apex to remove dead branches and query references Cleaning all FLS and UI metadata Removing indirect dependencies (formula fields, config mappings) Handling environment differences during destructive deployments Using pre-destructive changes in the pipeline to safely remove metadata This story reinforced that in Salesforce, unused does not mean unreferenced, and that proper field retirement is as much about dependency management and deployment sequencing as it is about data analysis. #Salesforce #Apex #SalesforceDev #SalesforceDeveloper #SalesforceDevOps #Metadata #CI_CD #EnterpriseSalesforce #TechnicalDebt #CleanArchitecture

4

1 Comment

Salesforce Architects are expected to think beyond Lookup vs. Master-Detail, but as data models span multiple platforms, understanding cardinality, ordinality, and ERD notation becomes essential. Caitlin Graaf breaks down how to read and design precise, platform-agnostic data models and why it matters more than ever. https://bit.ly/3Oh3rnJ #Salesforce

30

The night before a major Salesforce go-live…... Everything looked ready. Until a critical workflow failed during final UAT. Lead routing broke. Automation rules misfired. Dashboards showed incorrect data. One small configuration change - big business impact. That’s where structured Salesforce testing makes the difference. At KiwiQA Services, we don’t just test screens. We validate workflows, integrations, roles, automation rules, and performance - end to end. Because Salesforce success isn’t just about implementation. It’s about confidence at go-live. If you're rolling out or optimising Salesforce, let’s make sure it works exactly as your business expects. #SalesforceTesting #QualityEngineering #CRMTesting #AutomationTesting #KiwiQA

19

Most Salesforce environments fail compliance tests not because of Salesforce, but because of how they’re customized. At Syncing Soft, we design Salesforce architectures with: 🔐 Attribute-based access control (ABAC) 🧊 Masking for sensitive fields in reports & APIs 📜 Immutable audit trails for auditors and regulators Customization shouldn’t only improve efficiency. It should keep you compliant. #SalesforceCustomization #AIGovernance #DataSecurity #SalesforceConsulting #EnterpriseCompliance #SyncingSoft

1

1 Comment

A lot of talk about GraphQL and #PeopleSoft. The GraphQL "conversation" happens over HTTP, so that is straight Integration Broker. The key challenges are: 🔑 Where to store GraphQL queries/mutations and 🔑 How to safely pass values/parameters to GraphQL servers String concatenation and Message Catalog bind variables may lead to corrupt queries at best and injection attacks at worst. We cover all of these issues in our new module: GraphQL for PeopleSoft https://lnkd.in/dcWUkEd3

18

Did you know that Int4 Suite enables automated #MuleSoft integration testing? Watch this 2 minute explanation by Michał Lubczyński to learn more.

3

Fast pipelines require fast tests. Fast tests require clean code. It’s that simple. Join Pablo Gonzalez 🇨🇷 —Director of Product Management at AutoRABIT and author of Clean Apex Code—for a webinar focused on why most #Salesforce #DevOps efforts fall short, and how architecture is the missing link. Topics include: ✅ The impact of test speed on CI/CD ✅ Core principles from the Apex Well-Architected Framework ✅ How to build scalable, maintainable Apex Date: Tuesday, July 22, 2025 Time: 10 a.m. ET Register Here: https://bit.ly/3Tu6qbJ

17

1 Comment

Salesforce LWC Feature You Shouldn’t Ignore: State Management https://lnkd.in/gzK_VdyT As LWC applications expand, managing data across components can become increasingly challenging. State Management provides a solution by maintaining a central, reactive state, which supports a clean and scalable UI architecture. Key Functions: - atom() – Create reactive state - setAtom() – Update state - computed() – Auto-calculate derived values Benefits: - Single source of truth - Better performance and scalability - Cleaner code with fewer events and less prop drilling - Easier maintenance Where to Use: - Multi-step forms and wizards - Dashboards with shared data - Cross-component communication - Complex enterprise UIs Architect Tip: If your LWC relies heavily on events, it’s time to implement State Management. #Salesforce #LWC #StateManagement #LightningWebComponents #SalesforceArchitect #FrontendArchitecture #Agentforce #SalesforceDevelopment

21

1 Comment

Apex Cursors For years, handling large datasets in Salesforce meant choosing between complexity and limits — Batch Apex overhead, OFFSET-based pagination, heap pressure, and tricky recovery logic. Apex Cursors feel like Salesforce finally addressing that gap. Instead of forcing everything into Batch Apex, Spring ’26 introduces a cleaner way to process large SOQL results incrementally, without loading millions of records into memory. What stands out to me • Process up to 50M records • True chunked processing with built-in pagination • Significantly reduced heap pressure • Much cleaner code compared to Batch Apex • Extremely powerful when paired with chained Queueables Where I see this shining • High-volume data processing • Data migrations and archiving • Platform-level and package solutions • Advanced background workloads where control matters ⚠️ Important perspective This isn’t “Batch Apex is dead.” Batch Apex is still the best choice for: • Scheduled jobs • Stateful processing • Strong retry and fault tolerance Apex Cursors modernize how we think about data processing — not replace it. Spring ’26 gives architects another sharp tool. The real win is knowing when to use which. #Salesforce

10

1 Comment

Running Salesforce and Azure Synapse? Getting data from one to the other shouldn't require a full engineering project. GRAX makes it simple — connect your Salesforce org, run your initial replication, and GRAX handles everything from there: continuous updates, automated schema changes, and full support for custom objects. Your data lands in your Azure environment, ready for analytics, AI, and reporting. No ETL headaches. No cumbersome middleware. Just your Salesforce data, where you need it. Learn more about the integration 👇 https://getgrax.co/471yF95 #Salesforce #Azure

4

What if your Salesforce Screen Flows could collect payments? With KULTURRA, they can. In this video, see how to embed a payment component directly into a flow with no custom code needed. ✔ Collect payments via credit card or ACH ✔ Link payments to Opportunities, Quotes, or custom objects ✔ Trigger follow-ups automatically—all inside Salesforce Turn screen flows into "money flows". 👉 Learn more about Kulturra: https://kulturra.com/ 👉 Try it on AppExchange: https://lnkd.in/gpdTcj6 

9

I used Agentforce Vibes to turn a plain‑English requirement into a full Salesforce object model in seconds. A quick demo of how AI can speed up metadata design and development. Video below. #AgentforceVibes #SFSweepstakes.

8

🚀 Confused about when to use @AuraEnabled, cacheable=true, @wire, or Imperative Apex in LWC? Here's a breakdown that can help you choose the right approach for your Salesforce component development: 🔹 @AuraEnabled Exposes Apex methods to LWC. Best for imperative calls and DML operations (insert, update, delete). Cannot be used with @wire. 🔹 @AuraEnabled(cacheable=true) Used for read-only Apex methods. Enables client-side caching and can be used with @wire. Must not include DML or callouts. 🔹 @wire Ideal for reactive, auto-fetched data from Apex (when cacheable) or UI API (e.g., getRecord). Works great for loading data on component render and keeping it up to date. 🔹 Imperative Apex Used for on-demand actions—like form submissions or button clicks. Works with both types of Apex methods but bypasses caching even if the method is cacheable. 🔁 Use refreshApex() to manually refresh data fetched via @wire when using cacheable methods or Lightning Data Service. #Salesforce #LWC #LightningWebComponents #Apex #AuraEnabled #ImperativeApex #WireDecorator #refreshApex #SalesforceDeveloper #PerformanceMatters #Trailblazer #CleanCode

3