Skip to content

Salesforce Order Data Import

VIDEO TRANSCRIPT | Recorded: 2025-09-18 | Verify against current system state

Abstract

Working session demonstrating the Salesforce data import process for orders and order items. Shows deactivating flows before import (create fellow fee on new membership), running imports in configurable batch sizes (100-250 records), monitoring bulk data load job progress, re-enabling apex triggers and flows after import, and handling import timeframe issues. Discussion includes separating sync schedules for different object types and using CData DBamp for person record imports.

Key Procedures

  • Disable "create fellow fee on new membership" flow before order item import
  • Navigate to Setup > Flows, find flow, click Deactivate
  • Run order import script, expand timeframe if orders not picked up
  • Address errors fall out (address issues, out-of-scope orders)
  • Run SF import item script to prepare data
  • Run order item import in batches (100-250 recommended)
  • Monitor progress via bulk data load jobs (Setup > Bulk Data Load Jobs)
  • Re-enable apex triggers and duplicate rules after person imports
  • Re-enable fellow fee flow after order item import
  • Consider separating sync frequencies: accounts/users hourly, orders daily

Notable Statements

  • 0:00:14 "The orders were from a time period before what we've actually accepted as appropriate. So we just had to expand that timeframe."
  • 0:01:02 "It's doing the same thing... This is picking out the orders that should be included."
  • 0:01:25 "We need to disable this create fellow fee on new membership flow."
  • 0:04:43 "The order mirror is taking a really long time and I wonder if it's because we've added so many orders now."
  • 0:05:32 "Keith needs account users, a couple other things, but not all of this... orders, order items, things like that to run maybe once a day."
  • 0:11:42 "They asked us to not set the membership statuses. So I've commented those things out."
  • 0:17:44 "Running in batches is kind of nice because... now it's splitting it up and they're running consecutively."
  • 0:19:22 "The person script has been updated to use cdata dbm. So it's not going to run on your local box."

Systems & Configurations

Systems Mentioned

  • Salesforce (Orders, Order Items, Flows, Bulk Load Jobs)
  • DBamp (database connector)
  • CData (person record import)
  • SQL Server (SF staging)

Specific Configurations

Item Value/Setting Timestamp Notes
Order Item Batch Size 100-250 0:16:47 Configurable
Orders Imported ~50,000 0:00:54 Extra orders in draft
Order Items 8,878 records 0:15:35 From 76 orders
Flow to Disable Create Fellow Fee on New Membership 0:01:25 Required for import
Person Batch Size 10,000 0:18:47 Recommended
Environment SF Stage 0:16:47 Staging import

Credentials/Access Mentioned

  • SQL Server access for import scripts
  • Salesforce admin for flow/trigger management
  • VPN connection required

Errors & Troubleshooting

  • Issue: Orders not being picked up
  • Cause: Timeframe filter too restrictive
  • Resolution: Expand timeframe in import script

  • Timestamp: 0:00:14

  • Issue: Order mirror queries slow

  • Cause: Large order volume
  • Resolution: Separate sync schedules by object type

  • Timestamp: 0:04:43

  • Issue: I2C deployments overwriting configurations

  • Cause: Repo deployments reset settings
  • Resolution: Wait until after go-live for some changes
  • Timestamp: 0:09:35

Transcript Gaps & Quality Notes

  • Working session with Matt and team
  • Technical import process demonstration
  • Multiple speakers troubleshooting in real-time
  • Discussion of future sync architecture decisions
  • Membership status import commented out per I2C request