Amar
@AmarKumar9
Followers
109
Following
2K
Media
158
Statuses
4K
Salesforce Architect specializing in robust, scalable solutions on the platform. Passionate about Agentforce innovations.
Hyderabad, India
Joined June 2011
What model does Data Cloud use instead of ACID? It follows Big Data analytical architecture principles: #Saleforce #Data360 #Datacloud
0
0
0
Data Cloud is analytical: Designed for large-scale ingestion, unification, analytics Optimized for querying, aggregation, segmentation Stores event + batch + streaming data Not meant for real-time transactional updates
1
0
0
Salesforce CRM is transactional: Stores live operational records (leads, contacts, opportunities) Designed for fast writes, updates, real-time state management Works on record-by-record updates
1
0
0
Storage Flow Source (CRM / S3 / APIs / etc.) ↓ Data Stream → DLO (raw storage layer) ↓ Mapping ↓ DMO (structured operational model) ↓ Unified Individual / Calculated Insight / Activation
1
0
0
Data Cloud stores ingested data in a Data Lake Layer first, inside Data Lake Objects (DLOs). Then it maps into structured Data Model Objects (DMOs) used for identity resolution and activation.
1
0
0
Salesforce Data Cloud is a customer data platform that collects, stores, unifies, and activates data from multiple systems (CRM, S3, APIs, POS, mobile apps, loyalty apps) to create a single unified customer profile and enable analytics, segmentation, AI, and personalization.
3
0
0
I wrote a detailed breakdown of what failed, why it failed, and what finally worked in 2025. If you’ve ever built something that looked easy and broke in production, this is for you. 👉 Blog link in reply ⬇️ #Salesforce #LWC #ServiceCloud #ExperienceCloud #SalesforceDeveloper
2
0
0
Biggest takeaway? Modern Salesforce problems are rarely about Apex complexity. They’re about understanding navigation boundaries and state destruction.
1
0
0
The final solution uses: ✔ Apex (IDs only, cacheable) ✔ LWC lifecycle awareness ✔ URL-driven alignment ✔ Browser-level state persistence Not pretty — but correct.
1
0
0
The real fix wasn’t clever code. It was accepting Salesforce’s lifecycle constraints and designing around them. • URL = source of truth • State must be reconstructed • Persistence must live outside the component
1
0
0
I even evaluated the new LWC State Managers (Beta). Great for in-page coordination. Completely useless across record navigation. Why? Because JS memory doesn’t survive page boundaries.
1
0
0
Even worse: LWCs on record pages don’t automatically know which record is active. You must explicitly derive it from URL state (CurrentPageReference).
1
0
0
Every time you navigate to another record: • the page reloads • LWC memory is destroyed • local state resets If your solution relies only on component state, it will break.
1
0
0
On paper, record navigation is trivial: → fetch records → keep an index → navigate next / previous In reality, Salesforce record pages don’t behave the way most devs assume.
1
0
0
I thought I was building a simple “Next / Previous” button in Salesforce. It turned into one of my biggest platform lessons of the year.
1
0
0
If you want OAuth explained the way an architect would teach a curious developer, here’s the full blog: https://t.co/ciuEaPUFj2
agentblazer9.wordpress.com
The starting point: why OAuth matters Anakin Skywalker was the kind of developer who could wire up an integration in an afternoon. When he first had to connect an external app to Salesforce, his fi…
0
0
0
I also created a Jedi-style visual that explains OAuth flows in one glance. No jargon. No walls of text. Just a clean mental model for developers.
1
0
0
Anakin’s cheat-sheet: Web app → Web Server SPA / Mobile → User-Agent Backend automation → Client Credentials Backend acting as a user → JWT Bearer Long-lived → Use Refresh Token Simple. Intentional. Architected.
1
0
0
Every Salesforce dev must know the 4 main flows: • Web Server • User-Agent • Client Credentials • JWT Bearer Each solves a different problem. Wrong flow = brittle security
1
0
0