CONFIGURE COLUMNS
Nested JSON fields
Turn details inside structured JSON data into readable table columns, without reshaping the source file first.
What “nested” means
Rather than storing every detail side by side, a record can keep customer details in their own group. A path such as user.name tells Simple Tables: open user, then use name from inside it.
Show a detail from inside a group
In this example, user and order are groups. The paths below them point to the individual values you can show as columns.
[
{
"user": { "name": "Alice", "email": "alice@example.com" },
"order": { "id": 123, "total": 99.99 }
},
{
"user": { "name": "Bob", "email": "bob@example.com" },
"order": { "id": 124, "total": 149.5 }
}
]- user.name
- Alice
- user.email
- alice@example.com
- order.id
- 123
- order.total
- 99.99
Add a nested field
Open the available fields, select the path you need, and check the preview.
- 1
Open Add column
Edit the macro, switch to the Columns tab, and select Add column.
- 2
Find the path in Columns
Search by field name or path. Nested fields detected during import appear in the list.
- 3
Add the field
Select the path you need, such as user.name, then choose Add 1 column. The preview updates immediately.
- 4
Rename it if needed
Click the new column and replace the Header in Column details with a reader-friendly label. Save or publish the page when you are done.
Tip
You usually do not need to type a path. Search Add columns by field name or path. For a specific item in a list, a path such as items[0].price is also supported.
A simple example
A CRM team imports customer profiles where contact and account details are grouped together.
- Before
- Name, email, and account status sit inside the profile blocks. The key details are not visible as individual table fields.
- After
- The team adds user.name, user.email, and status.level as columns. They can read, sort, and filter the data directly in Confluence.