Memuat dalam Volume Besar

🌐 Juga tersedia dalam 19 bahasa

English · Español · 日本語 · Português (Brasil) · Français · Deutsch · Italiano · 한국어 · 简体中文 · Português (Portugal) · 繁體中文 · Türkçe · Polski · Tiếng Việt · ไทย · Українська · Español (México) · Français (Canada) · Deutsch (Schweiz)

Gambar dibuat dengan AI

Diterjemahkan dengan AI. Belum ditinjau oleh komunitas. Baca dalam bahasa Inggris Bagian ini telah berubah dalam bahasa Inggris dan belum diterjemahkan ulang. (52)

Modul 2 dari 5 dalam bab Migrasi dan Sinkronisasi, bab 10 kursus Data Architect. Setiap modul dapat dibaca secara mandiri. Sebelumnya: Migrasi Adalah Proyek Kualitas Terlebih Dahulu · Berikutnya: Otomasi Selama Pemuatan

Pertanyaan yang dijawab modul ini: Bagaimana Jumlah Nol mengubah cara Anda memuat data ke Salesforce?

Sepuluh rekaman? Saya hampir bisa mengetiknya. Seribu? Sekarang saya butuh alat. Sejuta? Itu masalah arsitektur. Operasinya tidak berubah (membuat atau memperbarui rekaman), tetapi Jumlah Nol mengubah cara saya melakukannya. Kita sudah melihatnya pada pemodelan, kueri, berbagi, dan integrasi, dan migrasi tidak berbeda. Pada volume besar saya peduli bagaimana saya memindahkan data, bagaimana saya memecahnya menjadi pekerjaan, dalam urutan apa ia berpindah, apa lagi yang sedang dikerjakan Salesforce saat saya memuat, bagaimana saya memulihkan ketika ada yang gagal, dan apakah saya bisa menjalankan semuanya lagi.

Start With the Picture

Same landscape, same amber arrow as module 1: RouteDesk’s open work coming into Salesforce the weekend RouteDesk retires. ⟲

Klik untuk memperbesar

Module 1 decided what moves on this arrow. This module is about how it moves. ⟲

Module 1 decided what comes in: the deliveries not yet made and the ones still inside the 60-day claim window, about 196,400 deliveries. Each one becomes a Work Order, with its line items (about 1.6 per delivery, so about 314,000) and its Service Appointment (about 196,400 more). That’s roughly 707,000 records, prepared in the preparation data store and ready to go. Not millions, but well past anything I’d send one record at a time. So, how do they get in? ⟲

Dok Muat di Belakang Bank

Ketika mengajarkan Bulk API, saya memakai bank. Anda masuk dengan setumpuk setoran, dan teller menerima 200 lalu menyuruh Anda kembali ke ujung antrean. Dengan sejuta rekaman, itu 5.000 kali antre, 5.000 panggilan API. Sementara itu sebuah truk berhenti di samping bank, menurunkan setoran dalam jumlah besar, dan dua puluh menit kemudian pergi sementara Anda masih antre. Itulah dok muat, dan namanya Bulk API.

The 200 is still real. A REST sObject Collections request takes “up to 200 records” (Create Records Using sObject Collections (terbuka di tab baru), REST API Developer Guide), and a SOAP create() call the same: “If a create request exceeds 200 records, then the entire operation fails” (create() (terbuka di tab baru), SOAP API Developer Guide; both checked 2026-10-27). Every 200 more records is another call. RouteDesk’s 707,000 records would be over 3,500 trips to the teller. ⟲

Klik untuk memperbesar

Same records, different door. ⟲

Dok muat punya lima langkah:

1. Buka job-nya. Tekan bel merah dan dapatkan tiket: ID job.
2. Unggah. Dok terbuka dan Anda memuat file CSV Anda dengan tiket itu, satu file atau seratus.
3. Tutup job-nya. Salesforce tidak tahu Anda sudah selesai sampai Anda menekan tombol biru besar: unggahan selesai. Sekarang ia mulai memproses.
4. “Sudah sampai belum?” Seperti anak-anak saya di kursi belakang: Anda bertanya, dengan ID job Anda, apakah sudah selesai. Sudah selesai? Sudah selesai?
5. Ambil hasilnya. Unduh rekaman yang berhasil (dengan ID Salesforce barunya) atau yang gagal (dengan error-nya).

Klik untuk memperbesar

Submit, wait, collect. ⟲

Sejuta rekaman hanya butuh segelintir panggilan, bukan ribuan. Tetapi perhatikan apa yang berubah: pekerjaannya asinkron. Anda tidak mendapat jawaban per rekaman; Anda mengirim, menunggu, dan mengambil. Jadi pemanggil perlu tahu apa yang dikirim, apa yang masih diproses, apa yang selesai, apa yang gagal, dan apa yang kembali. Itu bukan detail API. Itu kendali migrasi.

Dua Dok Muat: Bulk API 2.0 dan Bulk API

Ada dua versi, dan penting yang mana yang Anda pakai.

• Bulk API 2.0 is the one to start with. You upload the data for a job and Salesforce splits it into batches for you, retries for you and runs them in parallel. A job can take 150 MB, measured after Salesforce encodes it, so Salesforce advises uploading no more than 100 MB of CSV per job. ⟲
• Bulk API (1.0) makes you create the batches yourself, up to 10,000 records each. It’s older, but it still has two levers 2.0 doesn’t give you: serial mode for loads, and PK chunking for very large exports (module 5). ⟲

Both share a rolling 24-hour allowance of 15,000 batches, and either can load up to 150 million records in 24 hours. Job results are kept for seven days after the job completes (Bulk API and Bulk API 2.0 Limits and Allocations (terbuka di tab baru), checked 2026-10-27). Salesforce’s line between the doors: “Any data operation that includes more than 2,000 records is a good candidate for Bulk API 2.0”; below that, “bulkified” synchronous calls are fine (Loading Data from the API (terbuka di tab baru), Best Practices for Deployments with Large Data Volumes, Winter ‘27, checked 2026-10-27). Those are today’s numbers: check them before you plan around them. ⟲

Satuan, kelompok, dan massal adalah cara saya memikirkan bentuk pekerjaannya: satu pembaruan dari tindakan pengguna, beberapa ratus rekaman terkait dari sebuah proses bisnis, jutaan rekaman historis dalam migrasi. Itu bukan nama produk. Tanyakan bentuk pekerjaannya sebelum memilih alatnya.

Test knowledge. Know when the Bulk API is the answer: more than about 2,000 records, asynchronous, a job you submit and collect. Know the two versions apart: Bulk API 2.0 splits the batches for you and runs them in parallel; Bulk API (1.0) has you build batches of up to 10,000 records, and only it offers serial mode and PK chunking. Both share 15,000 batches in a rolling 24 hours. ⟲

Alat Tidak Menghapus Arsitektur

“Kita akan pakai Bulk API.” Oke. Itu tidak memberi tahu saya objek mana yang dimuat lebih dulu, insert atau upsert, apa kunci eksternalnya, bagaimana hubungan dibangun ulang, apa yang terjadi ketika sebagian rekaman gagal, apakah job bisa berjalan paralel, apakah pekerjaan paralel akan berebut induk yang sama, otomasi apa yang akan berjalan, atau bagaimana kita akan merekonsiliasi dan memulai ulang. Bulk API menyelesaikan masalah pengangkutan. Ia tidak menyelesaikan migrasinya.

The order comes from the model, and module 1 drew it for RouteDesk: reference data first, then the Work Orders, then their line items and appointments, then the claim Cases that point at them (Preserve the Source Identity, and Load by Keys). Each wave is its own job, and the next one doesn’t start until the last one’s results are in. Junction objects depend on two parents, self-referencing hierarchies may need several passes, and circular relationships may need records first and relationships second. Don’t discover these on cutover weekend. ⟲

Kadang Anda memuat rekamannya, lalu hubungannya. Sebuah perusahaan induk, anak perusahaan, dan anak perusahaan regional semuanya dibuat dalam migrasi. Alih-alih menyelesaikan setiap hubungan dalam satu putaran, muat akun-akunnya dengan kunci sumber yang stabil, lalu jalankan putaran kedua yang menetapkan hierarkinya. Gagasan yang sama membantu untuk self-lookup dan dependensi melingkar. Tujuannya bukan satu putaran. Tujuannya hasil yang deterministik dan bisa diulang.

Insert, Update, atau Upsert

Insert says create this as new. Update says I already know the Salesforce record I’m changing. Upsert says use this key to find out whether the record exists; update it if it does, create it if it doesn’t. With stable External IDs, upsert makes rehearsals far easier: load, find a transformation problem, fix it, rerun, without the run assuming everything is a first-time insert. Keys are architecture, not just integration plumbing. RouteDesk’s Work Orders upsert on the partner key, the same field the integration uses, so a manifest Redrock resends on cutover weekend updates the migrated record instead of duplicating it. ⟲

Upsert has a price, though. Salesforce’s own Large Data Volumes guide ranks the operations: “insert() is fastest, update() is next, and upsert() is next after that. If possible, also break upsert() into two operations: create() and update()” (Loading Data from the API (terbuka di tab baru), checked 2026-10-27). How do you know which records are new and which already exist? The preparation data store knows, because it pulled down what Salesforce already has and keeps the IDs that came back (module 1). So the 190,000 delivered Work Orders that nothing in Salesforce has touched can go in as a plain insert, and only the open ones the integration may already have created need the upsert. ⟲

Two more lines from the same guide. Load clean data: “Errors in batches trigger single-row processing for that batch, and that processing heavily impacts performance.” That’s module 1 paying off at the loading dock. And when you update, “send only fields that have changed.” A reload that resends every field of 196,400 Work Orders does work nobody asked for. ⟲

Tetapi upsert bukan sihir. Jika strategi kuncinya salah, operasinya salah. Dua rekaman sumber untuk pelanggan yang sama dengan kunci berbeda adalah dua rekaman bagi Salesforce; kunci sumber yang bisa mengidentifikasi beberapa target berarti kita salah memahami kardinalitasnya. Pekerjaan kualitas di modul 1 tetap penting; fitur API tidak menggantikannya.

Test knowledge. Insert is the fastest operation, then update, then upsert; Salesforce suggests splitting an upsert into creates and updates where you can. Upsert needs an External ID, and it’s what makes reruns safe. Load clean data, because errors in a Bulk API batch push that batch into slow single-row processing, and send only the fields that changed. ⟲

Paralel Lebih Cepat, Sampai Tidak Lagi

Pemrosesan paralel menaikkan throughput. Tetapi jika banyak rekaman dalam pemuatan menunjuk ke induk yang sama, transaksinya berebut kunci pada induk itu, dan apa yang kita lakukan agar lebih cepat justru menciptakan perebutan kunci, error, dan coba ulang. Itu titik panas bab 7 lagi: jika sejuta anak berkumpul pada beberapa induk, bentuk data penting bagi pemuatan. Ketika dua batch masing-masing menunggu kunci yang dipegang yang lain, Anda mendapat deadlock, dua mobil yang terjebak di persimpangan.

RouteDesk is exactly that shape. Almost 196,400 Work Orders, and nearly every one points at one of three Retail Partner Accounts. Load them in parallel in the order RouteDesk exported them, and every batch holds Work Orders for all three partners. ⟲

Klik untuk memperbesar

In export order, every batch needs every parent. One locks, the others wait. ⟲

Two levers. First, sort the files by parent, so the children of one parent travel together in the same batch instead of being spread across batches that collide. Salesforce gives the same advice: “When changing child records, group them by parent—group records by the field ParentId in the same batch to minimize locking conflicts” (Loading Data from the API (terbuka di tab baru), checked 2026-10-27). ⟲

Klik untuk memperbesar

Sorted by partner, each batch works on its own parent. ⟲

Second, on Bulk API 1.0, serial mode processes one batch at a time: slower, but it removes the contention. I reach for serial mode when the data is complex and we’re running into collisions and timeouts. Salesforce’s own guide is more cautious: serial mode “is used only when previously submitted asynchronous jobs have accidentally produced contention because of locks. Use only when advised by Salesforce” (Limits (terbuka di tab baru), Bulk API 2.0 and Bulk API Developer Guide, checked 2026-10-27). So sort first, and treat serial as the fallback. And it’s only on the older dock: Bulk API 2.0’s job reference says “Currently only parallel mode is supported,” and if other modes ever arrive, “the mode will be chosen automatically by the API and will not be user configurable” (Create a Job (terbuka di tab baru), Bulk API 2.0, checked 2026-10-27). A load that needs serial processing is a reason to use Bulk API 1.0. ⟲

Serial mode is a setting on the job, chosen when you create it. On Bulk API 1.0, RouteDesk’s Work Orders would be: ⟲

POST /services/async/68.0/job
{
  "operation": "upsert",
  "object": "WorkOrder",
  "externalIdFieldName": "Partner_Delivery_Key__c",
  "contentType": "CSV",
  "concurrencyMode": "Serial"
}

Leave concurrencyMode out and you get Parallel, the default. Salesforce’s job reference says when to change it: “If parallel mode results in too many failed records or failed jobs, submit the job with Serial concurrency mode,” and adds that it “can significantly increase the processing time” (JobInfo (terbuka di tab baru), Bulk API 2.0 and Bulk API Developer Guide, checked 2026-10-31). ⟲

And if three parents are too few for any sorting to help, look at the model. Checkpoint 1 already offered a way to spread them: link Work Orders to a child Account per distribution center, so nine parents share the load instead of three. That’s a design decision, made before the migration, not a loader setting. ⟲

Saya tidak mulai dengan “selalu paralel” atau “selalu serial”. Saya melihat bentuk hubungannya, induk-induk yang panas, otomasi yang berjalan, apa lagi yang mengunci, dan apa yang terjadi saat latihan. Lalu saya memilih. Benar dulu, baru cepat.

Test knowledge. Parallel loads lock parent records. When many children share a few parents, expect “unable to lock row” errors: sort the load file by parent so each batch touches as few parents as possible. Serial mode (Bulk API 1.0 only) removes the contention at the cost of speed; Salesforce reserves it for lock contention the sorting didn’t solve. ⟲

Ukuran Batch Adalah Keputusan Penyetelan

Orang ingin angka ajaib. Saya tidak punya. Ukuran yang tepat bergantung pada objek, kerumitan rekaman, otomasi, hubungan, penguncian, payload, dan mekanismenya. Terlalu besar, dan kegagalan menjadi mahal dan transaksi mengerjakan terlalu banyak; terlalu kecil, dan overhead mendominasi dan eksekusinya jauh lebih lama dari seharusnya (dan pada 1.0, menghabiskan jatah batch Anda). Mulailah di dalam batas yang didukung alatnya, lalu ukur dengan data yang representatif.

And the rehearsal data needs the same shape as production. Twenty million records in production, ten thousand in the test, and everything flies: what did we prove? Not much about scale. The test doesn’t need every record, but it must expose the architecture: heavy concentration on a few parents, millions of children, large text fields, complex relationships, historical skew, automation triggered by particular values. The Number of Zeros matters, and so does the shape behind the zeros. For RouteDesk that means a rehearsal set where a third of the Work Orders still point at Redrock. ⟲

Pengguna Pemuatan, dan Siapa Pemilik Rekamannya

For a substantial migration I want a dedicated migration identity, not someone’s personal admin account: for traceability, controlled permissions, automation decisions (module 3), monitoring and troubleshooting. A million records created by the migration user during cutover tells me something. A million created by Daniel Reyes because Daniel ran Data Loader on Saturday night mixes human identity with system activity. Give it the permissions the job needs, and don’t let it become a permanent mystery superuser nobody dares disable. ⟲

Then don’t confuse who loaded a record with who should own it. Created By is provenance; Owner is architecture, with sharing and business consequences. Set business ownership deliberately. Sometimes there’s no good answer in the source: the record’s owner left years ago, or never existed. It can be hard to assign records to active users, and I’ve created a dedicated “data load” user to own them. That’s sound practice with one condition from chapter 7: a user who owns more than 10,000 records of an object is ownership skew, so that owner should have no role, or a role of its own at the top of the hierarchy (Ownership Data Skew (terbuka di tab baru)), and the records should have a path to real owners. Who owns the records, and where that owner sits in the role hierarchy, is an important decision the team makes for any bulk import, not something the loader defaults. For RouteDesk’s Work Orders, chapter 7’s question decides it: does ownership drive who sees a delivery? At Steve Trucking it doesn’t (partners see their own deliveries through the partner on the record), so one owner with no role is fine. ⟲

Alat: Pilih demi Keterulangan

There are many ways to load data, and the tool matters less than how you use it. Salesforce’s Data Loader has been tried and true, but it’s aged: a desktop tool that works CSV by CSV. Its command-line version can be scripted and pointed at your preparation data store, which is how I’ve run repeated loads. Some tools connect a SQL database straight to Salesforce, copying data down and sending changes back with SQL. ETL and integration platforms do the same job at enterprise scale. And with the APIs you can drive the Bulk API directly: the Salesforce CLI’s sf data upsert bulk loads a CSV through Bulk API 2.0 with an External ID from one command (data upsert bulk (terbuka di tab baru), Salesforce CLI Command Reference, checked 2026-10-27). You can even have AI write the small scripts that run each complex step. ⟲

Apa pun alatnya, inilah preferensi terkuat saya: saya tidak ingin migrasi produksi menjadi kali pertama kita menjalankan migrasinya, dan saya tidak ingin setiap latihan menjadi petualangan buatan tangan. Jika langkah 17 berbunyi “buka CSV ini, urutkan menurut kolom G, hapus baris kosong, salin rumus ini ke bawah, lalu jalankan Data Loader dengan pengaturan ini,” saya gugup. Setiap langkah manual adalah peluang untuk file yang salah, baris yang terlewat, versi basi, pengurutan yang keliru, filter yang terlupa, pengaturan yang berbeda dari latihan. Sebagian mungkin tak terhindarkan: dokumentasikan dan uji. Tetapi tujuannya keterulangan, jadi ekstrak, transformasi, validasi, muat, tangkap hasil, dan rekonsiliasi harus berjalan dengan cara yang sama setiap kali.

Jika Anda menjadwalkan pemuatan, jangan jadwalkan lebih sering daripada yang bisa diselesaikannya. Job per jam yang kadang butuh sembilan puluh menit akan mulai menumpuk di atas dirinya sendiri; periksa bahwa eksekusi sebelumnya sudah selesai sebelum yang berikutnya dimulai.

Keep Every Result, and Bring the Keys Back

Untuk setiap pemuatan, simpan versi input, file muatan yang sudah ditransformasi, ID job, hasil berhasil dan gagal beserta error-nya, waktu, jumlah rekaman, dan output rekonsiliasi. Setelah migrasi besar, seseorang akan bertanya “apa yang terjadi dengan rekaman ini?” dan saya ingin bukti, bukan “kayaknya itu di CSV ketiga Sabtu pagi.” Hasil bulk hanya disimpan tujuh hari, jadi unduh sambil berjalan. Beri artefak-artefak ini siklus hidup nanti; jangan buang selagi Anda masih perlu membuktikan perpindahannya.

Then bring the keys back. The success results carry each record’s new Salesforce ID next to the key you sent. Write them back into the preparation data store, on the row that produced the record: that’s the last frame of module 1’s three sets of keys. On the Zendesk migration I described in module 1, that’s what made everything else possible. With the Salesforce IDs back on every row, I could load in phases (accounts and contacts first, then the cases, then the comments and files that hang off them), and each phase found its parents by the IDs the last one returned. I could do a partial load: just the rows that failed, or just one group. And I could reload: fix a transformation, regenerate the affected rows, and send only those, knowing exactly which Salesforce records they’d update. Without the keys back, every rerun is a guess. ⟲

Ukuran kegagalan juga soal Jumlah Nol. Dua puluh kegagalan dari 100 itu buruk; dua puluh dari 20 juta tetap perlu diselidiki tetapi sinyalnya berbeda. Perhatikan tingkatnya, bukan hanya jumlahnya, dan klasifikasikan kegagalannya: validasi, induk hilang, kunci duplikat, penguncian, tipe data, otomasi, izin. Setelah diklasifikasikan, mereka menunjukkan masalah arsitektur, bukan file error raksasa.

Dan kinerja lebih dari rekaman per detik. “Kami menggandakan throughput.” Apa yang berubah? Apakah penguncian, kegagalan, atau coba ulang naik? Apakah otomasi hilir tertinggal, penghitungan ulang berbagi menumpuk, integrasi lain kewalahan? Apakah total cutover benar-benar menjadi lebih singkat? Migrasi tidak berjalan dalam ruang hampa.

Test knowledge. The Bulk API’s success results return each record’s new Salesforce ID with the data you sent, and its failure results return each error; both are kept for seven days. Capture them, write the IDs back to the source or staging data, and you can load in phases, retry only the failures, and reconcile what landed. ⟲

Uji Seluruh Eksekusinya

Memuat akun, lalu kontak, lalu pesanan, masing-masing diuji terpisah, bukan migrasi yang sudah diuji. Saya ingin latihan penuh, dari awal sampai akhir, dengan urutan, transformasi, identitas, strategi otomasi, dan rekonsiliasi yang sama, pada volume yang representatif. Dependensi muncul di antara langkah: keterlambatan sepuluh menit memulai pemuatan berikutnya pada waktu yang salah, tingkat kegagalan yang tak terduga menghabiskan berjam-jam perbaikan, penghitungan ulang berbagi menggeser jadwal. Eksekusi penuh memberi tahu Anda apakah migrasinya berjalan, bukan hanya apakah setiap perintah berjalan.

If the rehearsal includes a performance or scale test, put Salesforce’s lead time in the plan. “All tests must be pre-approved. Unapproved testing is subject to throttling or blocking,” and for tests at 120 requests a second or below, the request goes in “at least one week before the testing date” (Salesforce Performance and Scale Test FAQs (terbuka di tab baru), Salesforce Help, checked 2026-10-27). A rehearsal that gets throttled proves nothing about cutover weekend. ⟲

AI Bisa Menulis Skripnya. Eksekusinya Tetap Tanggung Jawab Anda.

AI is very good at generating transformation scripts, load orchestration, error parsers, reconciliation queries and retry logic. Use it. But generated code can be wrong at enormous speed: a wrong transformation on ten records is ten fixes; on ten million, the Number of Zeros applies to the mistake too. The way I use it is step by step: clean, transform and migrate steps, with every generated command and action tracked. That’s deterministic, auditable automation, not unattended judgment. Test it at realistic scale before you trust it with production data. ⟲

Di luar ujian: apa yang diubah AI. AI menurunkan upaya membangun perangkat migrasi, dan membuat operasi massal lebih mudah dihasilkan dan dijalankan dengan cepat. Makin besar operasinya, makin kuat kebutuhan akan transformasi yang deterministik, langkah yang dilacak, latihan, kontrol, dan rekonsiliasi.

Yang Diputuskan Arsitek di Sini

• Mekanisme pemuatan dan versi API mana yang cocok dengan volume dan bentuk pekerjaannya, alih-alih memperlakukan migrasi seperti lalu lintas transaksional.
• Urutan objek dan hubungan yang digerakkan dependensi, termasuk kapan rekaman dan hubungan butuh putaran terpisah.
• Which operation each set of records gets (insert, update or upsert), based on what the preparation data store knows already exists. ⟲
• Where parallel processing is safe, and where concentration, locking or automation justify sorting by parent, a model change, or serial processing. ⟲
• Kunci stabil, identitas migrasi, kepemilikan rekaman, dan perangkat yang bisa diulang mana yang membuat latihan dan pemuatan produksi deterministik.
• How results and new IDs come back, so loads can run in phases, retry only failures, and reload safely. ⟲
• Bukti, klasifikasi kegagalan, dan latihan eksekusi penuh apa yang dibutuhkan sebelum memercayai prosesnya pada skala produksi.

Dok Muat Tetap Butuh Rencana

The loading dock moves enormous amounts of data. It doesn’t decide which truck unloads first, where the pallets go, which shipment belongs to which customer, what happens to a damaged pallet, whether two forklifts are using the same aisle, or whether everything that should have arrived did. That’s architecture. Know the Number of Zeros and the shape behind them. Load in dependency order, use stable keys, control concurrency, bring the keys back, make the process repeatable, keep the evidence, and rehearse the whole thing. Then use the loading dock as fast as the architecture safely allows. ⟲

Jelajahi

• Salesforce, Bulk API and Bulk API 2.0 Limits and Allocations (terbuka di tab baru), Developer Limits and Allocations Quick Reference, checked 2026-11-01. ⟲
• Salesforce, General Guidelines for Data Loads (terbuka di tab baru) and Limits (terbuka di tab baru), Bulk API 2.0 and Bulk API Developer Guide, checked 2026-11-01. ⟲
• Salesforce, Best Practices for Deployments with Large Data Volumes, Loading Data from the API (terbuka di tab baru), Winter ‘27, checked 2026-11-01. ⟲
• Salesforce, REST API Developer Guide, Create Records Using sObject Collections (terbuka di tab baru), checked 2026-11-01. ⟲
• Salesforce, SOAP API Developer Guide, create() (terbuka di tab baru), and Bulk API 2.0, Create a Job (terbuka di tab baru), checked 2026-11-01. ⟲
• Salesforce, Bulk API 2.0 and Bulk API Developer Guide, JobInfo (terbuka di tab baru) (the Bulk API 1.0 job fields, concurrencyMode), API version 68.0 (Winter ‘27), checked 2026-11-01. ⟲
• Salesforce Help, Salesforce Performance and Scale Test FAQs (terbuka di tab baru), checked 2026-11-01. ⟲
• Kursus Integration Architect: Bulk (coming soon) membahas Bulk API secara mendalam.
• Di kursus ini: Merancang untuk Skala (titik panas dan skew kepemilikan).
• Salesforce Developers, Designing Record Access for Enterprise Scale, Ownership Data Skew (terbuka di tab baru), checked 2026-11-01. ⟲
• Salesforce Developers, Salesforce CLI Command Reference, data upsert bulk (terbuka di tab baru), checked 2026-11-01. ⟲