Skip to main content
The extension ships with a one-click data seeder for evaluation tenants, training sandboxes, and demos. The seeder is idempotent — re-running it skips records that already exist, so it’s safe to run repeatedly.

​
Run the seeder

  1. In BC, open Tell Me (Alt+Q).
  2. Search for HR Demo Data Generator.
  3. Click Run Demo Seed on the page that opens.
A confirmation dialog summarises what was inserted, broken down per section.

​
What gets seeded

​
What it doesn’t seed

  • Standard BC master data (G/L accounts, currencies, payment terms, customers, vendors). The seeder assumes you started from a CRONUS or evaluation company that already has those.
  • Air Ticket Policy, EOS Config, Social Insurance Settings, Overtime Config, Vacation Time Setup, Compensation Allowances. These are higher-detail HR setup areas — configure them per the regulations you’re modelling. See Configure HR.
  • Posting groups for HR (Employees Leave Account, Employees Loans Account, etc. on the Employee Posting Group extension). Set these to G/L accounts that exist in your chart of accounts before posting any HR journal entries.

​
Removing demo data

There’s no “wipe” action — by design, partner tools should not delete customer data. If you need a clean slate:
  1. In a sandbox or test environment, drop and recreate the company. BC handles the schema reset.
  2. Or selectively delete the seeded records via the relevant list pages (Department List, Position List, etc.). The sample employee HR-EMP-001 and its dependent records (shift, leave, loan, installments) should be deleted in reverse order to avoid foreign-key violations.
Don’t use the seeder in production. The sample employee, loan and shift assignment are not part of your real HR data and can confuse downstream reporting. Production tenants should configure master data and create employees directly.

​
Source of truth