Posts

Salesforce Data Migration: Data Import Wizard vs Data Loader vs Data Loader CLI vs Bulk API

Image
  Introduction Data migration and data loading are common activities in Salesforce. Whether you're onboarding new customers, migrating legacy data, performing mass updates, or integrating with external systems, choosing the right tool is crucial. Salesforce provides multiple options: Data Import Wizard Data Loader Data Loader CLI Bulk API Each tool serves a different purpose and comes with its own limitations and advantages. 1. Data Import Wizard What is Data Import Wizard? Data Import Wizard is a browser-based data import tool available directly within Salesforce Setup. It is designed for administrators and business users who need a simple way to import data without installing software. According to Salesforce, Data Import Wizard supports: Accounts, Contacts, Leads, Solutions, Campaign Members, Person Accounts, and Custom Objects . It supports imports of up to 50,000 records at a time . It does not support many standard objects , such as Opportunities, Cases, Products, and others,...

Integrating Salesforce with External Billing Systems Using Platform Events

Image
 Requirement:   Whenever Opportunity becomes Closed Won, create an Invoice in Billing System. Business Scenario:   ABC Technologies purcheses an Internet Package worth $50,000. 1.Customer     : ABC Technologies 2.Product        : Internet Package 3.Amount        : $50,000 4.Opportunity  : Closed Won Instead of directly calling Billing API from the Opportunity Trigger:      Opportunity  => Platform Event => Billing Systen External System setup: Step 1: Create MockAPI Account Website:      https://mockapi.io Actions: open sign up & login. Step 2: Create Project -click New Project         Name - Salesforce Billing System Step 3: Create Invoice Resource       Inside Project:           create Resource:                   Resource Name - Invoices Fields: ...

Salesforce Integration Basic Details

I’ll explain with 3 scenarios : Salesforce → External System (one-way) External System → Salesforce (one-way) Two-way (bi-directional) And in between, I’ll clarify Named Credentials, Connected Apps, OAuth, Client Id/Secret, API key, etc. 🔹 Step 1: Core Building Blocks in Salesforce Integrations 1. Named Credential What it is: A secure way in Salesforce to store external endpoint URL + authentication method (OAuth, Basic, API key). So your Apex code doesn’t hardcode credentials. Why we use it: ✅ Centralized credential management ✅ No need to store username/password in code ✅ Auto handles token refresh (if OAuth) When to use: Whenever Salesforce needs to call an external system . 2. Connected App What it is: A configuration in Salesforce that allows an external system to connect into Salesforce using OAuth. Why we use it: ✅ If an external system needs to call Salesforce APIs (REST, SOAP, Bulk) ✅ Provides Client Id + Client Secret When to use: When...

Oracle to Salesforce Integration: Handling Inbound REST API

Image
  Introduction This blog extends our previous guide on Salesforce-to-Oracle outbound integration by focusing on an inbound REST API integration where Oracle sends customer data (including Orders and Addresses) to Salesforce to create or update records. We’ll provide a detailed Apex REST service with comprehensive comments to explain the @RestResource and @HttpPost annotations and their purpose. Additionally, we’ll clarify when and how to use a Named Credential in inbound integrations, particularly for scenarios requiring outbound callbacks to Oracle. This guide is beginner-friendly, assuming basic Salesforce admin/developer knowledge and familiarity with the objects from the outbound integration. Use Case When a customer record is updated in Oracle (e.g., status changes or new orders are added), Oracle sends a REST API request to Salesforce to: Update or create a Customer__c record and its related Order__c and Address__c records. Log the request and response in Integration_Lo...