Enrico MURRU 💡

Most people don’t even know there are two types of Salesforce IDs. Let alone why it matters. → 15-digit → 18-digit Looks the same. But here’s the deal: The 15-digit ID is case-sensitive. The 18-digit ID is not. That tiny difference? Can break your integration. Can confuse your Excel formulas. Can make your VLOOKUP cry. Salesforce uses 15-digit IDs inside the system. But 18-digit IDs outside — for tools, reports, and API work. So if you’re exporting data… And your joins aren’t working... You might be using the wrong one.  Trust me — One small digit can waste hours of your time. Working with Salesforce means knowing the details that don’t show up on the surface. This is one of them. 🧠 Pro tip: Use CASESAFEID() in formulas to get the 18-digit version instantly.    For more Salesforce insights like this — Follow Creatique Technologies 🔍 

159

8 commenti

🔥 𝐁𝐮𝐢𝐥𝐝 𝐌𝐮𝐥𝐭𝐢 𝐀𝐠𝐞𝐧𝐭 𝐈𝐧𝐭𝐞𝐫𝐚𝐜𝐭𝐢𝐨𝐧𝐬 𝐮𝐬𝐢𝐧𝐠 𝐌𝐨𝐝𝐞𝐥𝐬 𝐀𝐏𝐈 𝐢𝐧 𝐌𝐮𝐥𝐞𝐒𝐨𝐟𝐭 ✨  As part of our multi agents demo, we are providing different types of agent templates for building or wrapping A2A conform agents in MuleSoft. In this post, I’d like to spotlight a 𝐃𝐨𝐦𝐚𝐢𝐧 𝐀𝐠𝐞𝐧𝐭 built completely with the 𝐌𝐨𝐝𝐞𝐥𝐬 𝐀𝐏𝐈 𝐥𝐞𝐯𝐞𝐫𝐚𝐠𝐢𝐧𝐠 𝐭𝐡𝐞 𝐄𝐢𝐧𝐬𝐭𝐞𝐢𝐧 𝐓𝐫𝐮𝐬𝐭 𝐋𝐚𝐲𝐞𝐫 as an example designed to interact with 𝐬𝐩𝐞𝐜𝐢𝐚𝐥𝐢𝐳𝐞𝐝 𝐚𝐠𝐞𝐧𝐭𝐬. This solution is fully implemented in MuleSoft, leveraging the Einstein Connector for robust integration and performance. In total we built 5 Mule flows for this domain agent. (𝘺𝘦𝘴 𝘰𝘯𝘭𝘺 5 𝘧𝘭𝘰𝘸𝘴) 📌 𝒂𝒏𝒔𝒘𝒆𝒓-𝒑𝒓𝒐𝒎𝒑𝒕-𝒇𝒍𝒐𝒘 - The main flow, taking in the user query and holding all subflows. 📌 𝒔𝒆𝒕-𝒂𝒏𝒅-𝒊𝒏𝒊𝒕𝒊𝒂𝒍𝒊𝒔𝒆-𝒗𝒂𝒓𝒔 - This flow mainly collects all informations coming in by the user and save it into variables. 📌 𝒑𝒓𝒐𝒄𝒆𝒔𝒔-𝒖𝒔𝒆𝒓-𝒒𝒖𝒆𝒓𝒚 (Create Plan) - This flow is for reasoning and planning upon user request and available agents. We've used, 1️⃣ MuleSoft Inference to leverage 𝘖𝘱𝘦𝘯𝘈𝘐 𝘔𝘰𝘥𝘦𝘭𝘴 (𝘨𝘱𝘵-4𝘰-𝘮𝘪𝘯𝘪) 𝒕𝒐 𝒄𝒓𝒆𝒂𝒕𝒆 𝒕𝒉𝒆 𝒑𝒍𝒂𝒏 2️⃣ MuleSoft Inference to leverage 𝘖𝘱𝘦𝘯𝘈𝘐 𝘔𝘰𝘥𝘦𝘭𝘴 (𝘨𝘱𝘵-4𝘰-𝘮𝘪𝘯𝘪) 𝒕𝒐 𝒓𝒆𝒂𝒔𝒐𝒏 𝒖𝒑𝒐𝒏 𝒂𝒗𝒂𝒊𝒍𝒂𝒃𝒍𝒆 𝒂𝒈𝒆𝒏𝒕𝒔 📌 𝒓𝒆𝒑𝒍𝒂𝒏-𝒂𝒏𝒅-𝒂𝒔𝒔𝒆𝒔𝒔-𝒖𝒔𝒆𝒓-𝒒𝒖𝒆𝒓𝒚 (Replan) - Validates the current observation and answers provides by specialised agents and replans by calling the 𝒑𝒓𝒐𝒄𝒆𝒔𝒔-𝒖𝒔𝒆𝒓-𝒒𝒖𝒆𝒓𝒚 again. 📌 𝒔𝒆𝒏𝒅-𝒕𝒂𝒔𝒌𝒔-𝒕𝒐-𝒔𝒑𝒆𝒄𝒊𝒂𝒍𝒊𝒔𝒆𝒅-𝒂𝒈𝒆𝒏𝒕𝒔 - Is called by 𝒑𝒓𝒐𝒄𝒆𝒔𝒔-𝒖𝒔𝒆𝒓-𝒒𝒖𝒆𝒓𝒚 flow to execute specialised agents. We've used 2 Connectors: ✅ 𝐌𝐮𝐥𝐞𝐒𝐨𝐟𝐭 𝐄𝐢𝐧𝐬𝐭𝐞𝐢𝐧 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐨𝐫 ✅ 𝐌𝐮𝐥𝐞𝐒𝐨𝐟𝐭 𝐀2𝐀 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐨𝐫 Thats it, no more flows, just 5 flows to create a powerful domain agents, which is capable of reasoning, planning, assessment and replan if needed to answer a users questions. This is the domain agent template for multi agent interactions in MuleSoft and is 𝐚𝐯𝐚𝐢𝐥𝐚𝐛𝐥𝐞 𝐨𝐧 𝐨𝐮𝐫 𝐆𝐢𝐭𝐡𝐮𝐛 𝐎𝐫𝐠: https://lnkd.in/eimYVAkK 📌 𝐋𝐞𝐚𝐫𝐧 𝐦𝐨𝐫𝐞 𝐚𝐛𝐨𝐮𝐭 𝐭𝐡𝐞 𝐌𝐨𝐝𝐞𝐥𝐬 𝐀𝐏𝐈: https://lnkd.in/ePWp2PBT 📌 𝐋𝐢𝐧𝐤 𝐭𝐨 𝐭𝐡𝐞 𝐌𝐮𝐥𝐭𝐢 𝐀𝐠𝐞𝐧𝐭 𝐃𝐞𝐦𝐨: https://lnkd.in/eQwqTweP 📌 𝐋𝐞𝐚𝐫𝐧 𝐦𝐨𝐫𝐞 𝐚𝐛𝐨𝐮𝐭 𝐭𝐡𝐞 𝐌𝐮𝐥𝐞 𝐀𝐈 𝐂𝐡𝐚𝐢𝐧 𝐏𝐫𝐨𝐣𝐞𝐜𝐭: mac-project.ai #salesforce #mulesoft #a2a #agentforce #tools

229

5 commenti

🔐 Ready to invest into this 5 mins video about Remote Site Settings vs Named Credentials vs Connected App? If you’ve ever worked on Salesforce integrations, you’ve likely met these three—but knowing when and why to use each is key. 1️⃣ Remote Site Settings Think of it as a gate pass in Salesforce. Before making an HTTP callout to an external URL, you need to whitelist that domain here. 📌 Only the URL is stored—no credentials. 📌 Mandatory for callouts unless you use Named Credentials. 2️⃣ Named Credentials Your integration passport. It stores: ✔️ Endpoint URL ✔️ Authentication method (Basic, OAuth 2.0, JWT, etc.) ✔️ Username/Password or Token 🚀 No need to handle authentication in Apex—it’s handled automatically! ✨ Bonus: Works with Auth Providers to simplify OAuth flows. 3️⃣ Connected App Your Salesforce handshake for OAuth. Created on Salesforce when another application wants to connect using OAuth 2.0. You define: ✔️ OAuth scopes (what data the app can access) ✔️ Callback URL ✔️ Consumer Key & Secret for the client app

99

15 commenti

🚀 Salesforce Winter '26 Flow Updates Are Here! ❄️ Winter is coming… and so are powerful new Flow features! 💡 This release takes automation to the next level, empowering admins and developers to create seamless, intelligent, and dynamic processes. ✨ Top Highlights: 1️⃣ Flow Version Comparison :– Easily track changes between versions to debug and optimize like a pro. 2️⃣ AI-Driven Decision Criteria :– Leverage AI to make smarter, data-driven automation decisions. 3️⃣ Screen Flows in Experience Cloud (Beta) :– Build guided experiences for customers and partners, blurring internal and external processes. 4️⃣ Apex-Defined Data Types :– Pass complex data structures directly into your flows for next-level automation. 5️⃣ Improved Debugging Panel :– A cleaner, more efficient way to test and troubleshoot flows. 💭 Which feature excites you the most? Drop your favorite update in the comments below! 👇 #Salesforce #Winter26 #FlowBuilder #Automation #Apex #AI #ExperienceCloud #SalesforceDeveloper #NoCode #LowCode #Innovation #DigitalTransformation #DevBuddySFDC Salesforce Trailhead Trailhead by Salesforce

99

2 commenti

20 Salesforce architects. 1 complex challenge. Only 10% got it right. The difference? They didn't jump to a "safe" technical solution. The 10% who succeeded used DSQ—perfect for whiteboard sessions and CTA exams when details are scarce but complexity is high: - Distill - Cut through noise to find the essence - Simulate - Decompose and model the solution - Quantify - Reveal the real impact DSQ is just one framework we teach. Master them all in our October CTA cohort (starts 10-OCT) 👇 Link in comments 🔔 Follow me for more weekly challenges to level up your architect skills #salesforce #salesforcearchitects #JourneyToCTA

50

1 commento

Just published a new post on handling errors in custom LWC components for Salesforce Commerce Cloud checkout. I walk through two key patterns I’ve used: • Local error handling (like inline form validation and 3rd-party service errors) • Global error notifications using Salesforce’s built-in methods These patterns help keep the checkout experience clean and user-friendly—even when things go wrong. Check it out here 👉 https://lnkd.in/gJvtdecM Would love to hear how others are handling this in their custom builds. #Salesforce #LWC #CommerceCloud #DeveloperTips #ErrorHandling #commercecrew

68

1 commento