WPS Parent-Child Records is a hierarchy management feature in WPS tables for structured data workflows; it includes 4 core tasks, with 4 available without membership and 0 membership-related items.
At a Glance
| Metric | Value | Notes |
|---|---|---|
| Core tasks | 4 | Matches the number of rows in the How-to Index |
| Available without membership | 4 | Matches the number of Free rows in the index |
| Membership-related items | 0 | Matches the number of membership-related rows in the index |
| Version limit | None specified | No version gate is described for this feature |
About This Feature
Overview
Parent-Child Records lets you organize records in a WPS table with a hierarchy, making it easier to show parent tasks and subtasks or main items and child items in a structured view.
Main capabilities include:
- Create hierarchical relationships between records.
- Show records by level in views such as board and gallery.
- Expand or collapse child records when reviewing layered data.
- Keep hierarchy logic in place without changing formula calculations or summary results.
This feature fits task breakdowns, project node tracking, process management, and structured data organization in WPS Office on Windows.
System Requirements
| Item | Requirement |
|---|---|
| Operating system | A Windows PC that can run WPS Office normally |
| App version | The latest version of WPS Office is recommended |
| Network | An internet connection is needed when opening online tables or syncing data |
| Other | You need an editable table and permission to modify its records |
Source: WPS system requirements
Download & Installation
Before using Parent-Child Records, install WPS Office on your Windows device and open the target table for setup.
| Item | Details |
|---|---|
| Official download | WPS Office Free Download |
| Post-install check | Launch WPS Office, open a table, and confirm that the Child Record entry is visible on the top toolbar |
Source: WPS download page
Compare with Alternatives
| Dimension | WPS | Microsoft | Notion | Adobe | |
|---|---|---|---|---|---|
| Capability Summary | WPS tables support parent-child record relationships, hierarchical display in views, and expand/collapse for child records. | Microsoft documents indented hierarchy lists with parent and child rows and collapsible tree display in list pages. | Google Sheets supports grouped rows or columns with plus and minus controls to expand or collapse grouped content. | Notion databases support sub-items, letting teams create parent and child items and show them across database views. | Adobe Acrobat focuses on PDF editing, conversion, signing, and sharing rather than native parent-child record hierarchy management. |
| WPS Advantages | Advantage: WPS lets you build record hierarchy directly inside the same table and use it together with view-based display and expand/collapse behavior. | Compared with WPS: the official Microsoft page focuses on indented list presentation rather than direct hierarchy management inside a general online table. | Compared with WPS: Google Sheets grouping is useful for spreadsheet organization, but it is not described as record relationship management. | Compared with WPS: Notion also supports parent-child items, but the setup is centered on database settings and task-style databases. | Compared with WPS: Acrobat does not provide a native equivalent for record hierarchy management in table data. |
| Official Source | — | Designing Indented Hierarchy Lists | Freeze, group, hide, or merge rows & columns | Sub-items & dependencies | Acrobat features |
Overall Conclusion
WPS Parent-Child Records is a practical fit when you need to maintain record hierarchy directly in table-based data, such as task breakdowns, node tracking, and layered data views. Compared with general grouping tools or PDF products, it is closer to record relationship management. Compared with task-focused databases, the setup path is more direct for table workflows.
Use Cases
| No. | Scenario | Suitable for | Main challenge | How this feature helps |
|---|---|---|---|---|
| 1 | Project task breakdown | Project managers, contributors | Parent tasks and subtasks are mixed together | Build a task tree with parent and child records |
| 2 | Process node management | Operations teams, process owners | Multi-step workflows lack clear hierarchy | Set main steps as parent records and detailed steps as child records |
| 3 | Customer issue follow-up | Support and service teams | One issue may contain many follow-up actions | Use a parent record for the issue and child records for each action |
| 4 | Content planning | Editors, marketing teams | Topics and subtopics are hard to organize together | Structure topics, subtopics, and execution items with hierarchy |
| 5 | Layered data review | Team collaborators | Large record sets are hard to scan quickly | Expand or collapse levels as needed |
Membership & Benefits
Free vs WPS Premium
| Capability | Free users | WPS Premium |
|---|---|---|
| Writer, Spreadsheet, and Presentation basics | ✅ Available | ✅ Available |
| Basic Parent-Child Records usage | ✅ Available | ✅ Available |
| Basic PDF tools | ✅ Partly available | ✅ More advanced tools |
| Templates and cloud storage | Basic templates and 1 GB cloud storage | More advanced templates and higher cloud storage |
| AI and selected advanced tools | Limited access | More usage and advanced features |
Source: WPS Office pricing page
Recommendations
| Scenario | Recommended plan | Why |
|---|---|---|
| Daily table work with Parent-Child Records | Free | The feature description shows no membership restriction for the core workflow |
| Workflows that also need more PDF tools, advanced templates, or AI features | WPS Premium | Better for users who want broader office capabilities beyond the core hierarchy feature |
How to Subscribe
- WPS membership center: Subscribe now
- On the pricing page, you can review available plans and choose the option that fits your workflow.
Source: WPS Office pricing page