Feature Deep-Dive

Every feature built for
Salesforce developers specifically.

Not a generic data tool retrofitted for Salesforce. SproutEzee was designed from the ground up around how Salesforce orgs actually work — schemas, validation rules, relationships, and Bulk API.

Feature 01

Schema-Aware Generation

SproutEzee calls your Salesforce Metadata API to load every object and field definition the moment you connect. Custom objects ending in __c, managed package objects, platform events — all available instantly without any manual configuration.

Required fields are automatically included and populated. Optional fields can be toggled on or off. SproutEzee knows the difference between Text, Number, Currency, Email, Phone, Picklist, Date, DateTime, Lookup, and MasterDetail field types and generates appropriate values for each.

  • Auto-discovers all standard and custom objects from Metadata API
  • Reads picklist value sets — never generates invalid picklist values
  • Enforces field length limits — text fields never exceed maxLength
  • Number fields respect digit and decimal precision settings
Schema loaded — Contact object 47 fields
FirstNameUK First NameText(40)
LastNameUK Last NameText(80) ★
EmailRandom EmailEmail
MobilePhoneUK PhonePhone
LeadSourcePicklist: RandomPicklist(9)
NI_Number__cUK NI NumberText(11)
Annual_Income__cNumber: 20k–200kCurrency(2)
★ Required field — always included
Feature 02

Relationship-Aware
Generation

Salesforce data is relational. A Case needs an Account. A Contact needs an AccountId. An Opportunity needs a related Contact. Getting this wrong means failed inserts and broken lookup fields.

SproutEzee reads your org's relationship graph and sorts objects in correct dependency order. It generates parent records first, then populates lookup fields in child records with the correct IDs from the just-created parents.

  • Topological sort of object dependencies ensures correct insert order
  • Lookup fields populated from IDs of records generated in same run
  • Alternatively link to existing records already in your sandbox
  • Configurable ratio — e.g. 3 Contacts per Account on average
Generation Order — Inferred from Schema
Account 100 records Insert 1st
Contact AccountId Insert 2nd
Opportunity AccountId Insert 2nd
Case AccountId + ContactId Insert 3rd
500 Contact · 100 Account · 50 Opportunity · 200 Case — all inserted in correct order automatically.
Feature 03

UK Locale Data

Generic data generators produce American names, US zip codes, and SSNs. That's not useful if your Salesforce org serves UK customers. SproutEzee generates data that looks and feels like real UK records — because edge cases in UK formats are exactly what you need to test.

Names are drawn from the ONS most common UK forenames and surnames. Addresses follow the Royal Mail format. Phone numbers use the Ofcom numbering plan. NI numbers follow the valid format specification.

  • UK names from ONS most common forenames and surnames databases
  • Valid UK postcodes distributed realistically across regions
  • Phone numbers in 07xxx, 01xxx, 02xxx formats per Ofcom plan
  • NI numbers in valid format (NN NN NN NN A, no invalid prefixes)
  • Sort codes and bank account numbers in correct UK formats
First Name
Oliver
Last Name
Patel
Mobile Phone
07700 900 342
UK Postcode
B4 7NT
NI Number
KP 74 81 29 D
Sort Code
20-42-17
Bank Acct
73841920
Email
o.patel_k2@testdata.invalid
Feature 04

Validation Rule
Compliance

Validation rules are the leading cause of failed data imports. A rule like "Phone must start with 07 for Mobile" or "NI Number must match [A-Z]{2}[0-9]{6}[A-D]" will reject records that a generic generator creates.

SproutEzee pulls all active validation rule formulas via the Metadata API before generation. It evaluates each candidate record against those rules and regenerates any value that would trigger a failure — before the Bulk API is ever called.

  • Reads all active validation rules from Metadata API
  • Evaluates formula conditions against each generated record
  • Regenerates offending values — max 5 attempts per record
  • Reports any rules that couldn't be satisfied so you can investigate
Validation Rules — Contact 3 active rules
Phone_Must_Be_UK
NOT(REGEX(MobilePhone, "^07[0-9]{9}$"))
Pass — generated values match UK mobile pattern
NI_Number_Format
NOT(REGEX(NI_Number__c, "^[A-CEGHJ-PR-TW-Z]{2}[0-9]{6}[A-D]$"))
Pass — UK NI pattern applied automatically
Email_Must_Not_Be_Real
NOT(CONTAINS(Email, "testdata.invalid"))
Pass — testdata.invalid domain used by default
All 3 rules satisfied — 500 records cleared for Bulk API insert
Feature 05

Saved Data Templates

The most painful part of sandbox refreshes isn't the first time you set up test data. It's the tenth. Every two-week sprint has a refresh, and you rebuild the same records every time.

SproutEzee lets you save any field configuration — object, fields, patterns, volume, relationships — as a named template. After a refresh, run "Standard Contact Set" in one click. 500 records. 60 seconds. Done.

  • Save after any generation run — one click, named template
  • Templates include objects, field configs, patterns, volume, and relationships
  • Share templates with team members (Pro plan)
  • Duplicate and modify templates — sprint-specific variations
Standard Contact Set
500 Contacts · Account · 8 fields · UK locale
Run
Full Account Hierarchy
100 Accounts · 300 Contacts · 50 Opportunities
Run
Complex Case Scenario
200 Cases · 50 Accounts · Priority/Status mix
Run
Opportunity Pipeline
75 Opps · Stage distribution · £5k–£200k values
Run
Feature 06

Volume Generation
via Bulk API v2

When you need to test performance, governor limits, or list view scalability, you need thousands of records — not hundreds. SproutEzee uses Salesforce's Bulk API v2 for every insert, which bypasses trigger governor limits and processes records in large parallel batches.

Pro plan supports up to 10,000 records per generation run. Processing runs in background batches so you're not blocked waiting. You get a notification when the job is complete.

  • Bulk API v2 — handles 10,000+ records per job
  • Parallel batch processing — 500 records in ~60 seconds
  • Background processing — use Salesforce while inserts run
  • Volume selector: 10 / 50 / 100 / 500 / 1,000 / 5,000 / Custom
500
records
~60 seconds
1k
records
~2 minutes
5k
records
~8 minutes
10k
records (Pro)
~15 minutes
Estimates for Contact records with 8 fields via Bulk API v2. Times vary by org size, field complexity, and validation rule count.
Why SproutEzee

How we compare to the alternatives

The honest comparison — what SproutEzee does, what the alternatives do, and what your QA team actually needs.

Capability SproutEzee Manual Creation Mockaroo Apex Test Factories SF Data Generator
Reads your org's schema automatically Yes No No Partial Yes
Respects validation rules Yes Sometimes No Partial No
UK locale data Yes Manual Generic No US default
Handles lookup relationships Yes Manual No Code required Recipe required
Inserts via Bulk API v2 Yes No No No Yes
No code / no CLI required Yes Yes Yes Apex required SFDX + recipes
Saved reusable templates Yes No Schemas only No Recipe files
500 records in under 60s Yes 30-90 min Export only Gov limits Yes
Visible in Salesforce UI immediately Yes Yes Manual import Test class only Yes
Start Today

See these features in your own org.

Connect your sandbox for free. 100 records per day, 5 standard objects, full UK locale patterns — no credit card needed.