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
- In BC, open Tell Me (Alt+Q).
- Search for HR Demo Data Generator.
- Click Run Demo Seed on the page that opens.
A confirmation dialog summarises what was inserted, broken down per section.
What gets seeded
| Section | Records | Notes |
|---|
| Departments | ENG, HR, FIN, SAL, OPS | Engineering, Human Resources, Finance, Sales, Operations |
| Branches | HQ, BR2 | Head Office and Secondary Branch |
| Work Types | FT, PT, CON | Full-time, Part-time, Contractor |
| Nationalities | SA, EG, IN, PK, PH | Saudi, Egyptian, Indian, Pakistani, Filipino |
| Religions | Islam, Christianity, Other | |
| Genders | Male, Female | |
| Employee Document Types | Passport, National ID, Iqama / Residence Permit, Driving License, Educational Certificate | |
| HR Document Request Types | SAL-CERT, EMP-LET, EXP-LET, NOC-LET | Salary certificate, Employment letter, Experience letter, No-Objection Certificate |
| Positions | 6 sample roles | Software Engineer, HR Manager, Accountant, Sales Representative, Operations Lead, Project Manager |
| Leave Types | ANNUAL, SICK, UNPAID, EMERG | |
| Leave Configs | ANN-21D (21 days/year), SCK-14D (14 days/year) | |
| Shift Configs | DAY (9-5 with 1h break), NIGHT (10pm-6am with 1h break) | Each with timed work / break lines and weekend days |
| Sample Employee | HR-EMP-001 Layla Almasri | Software Engineer, Engineering / HQ, Saudi |
| Employee Shift | Day shift Jan 1 – Dec 31 2026 | |
| Employee Leave | One annual-leave row to seed balance | |
| Employee Loan | 6,000 across 12 × 500 starting Jan 2027 | Triggers automatic generation of the 12 installments |
| Announcement | One Info-severity welcome message | Visible for 30 days |
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:
- In a sandbox or test environment, drop and recreate the company. BC handles the schema reset.
- 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
| |
|---|
| Codeunit | Cod70003200 HR Demo Data HAC |
| Page | Pag70003200 HR Demo Data Generator HAC |
| Permission | Granted by Human Resource HAC permission set |
