Populating demo data keeps the demo tenant to its eight services

When the demo services took the standard names, Populate demo data on Configure > Demo data added the renamed services next to the old ones instead of replacing them. A tenant populated before the rename could end up with thirteen services, and skills still linked to the old ones. Only a demo reset tidied it up.

Populating now finishes with the same eight services a reset gives:

• A service still under its old name takes its new name and stays the same service, so its requests, products and skills come with it.
• Where the old and the new service both exist, everything on the old one moves to the new one and the old one is archived. That covers requests, product links, lead form choices, skills and a saved filter on the requests list.
• Each demo skill is linked to its services again on every run.
• Services you added to the demo tenant yourself are left as they are.

No request’s price or value changes. After a run, the summary shows how many services were renamed and how many were merged; both read 0 once the tenant is up to date.