> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data/computed-fields/formulas/parse-json-fields.md).
# Parse JSON Fields
Parse JSON to create new columns with the data you want
If your dataset has a field that contains data in a JSON format, you can parse that field to display the specific pieces of data you want in new columns. You can do this by creating a new custom field and then passing it a value that references the JSON field.
Let's explain this more in-depth by using the following example.
Suppose you have a field that has JSON data like the following:
```javascript
{
"fields": {
"pricing": {
"integerValue": "109"
},
"quantity": {
"integerValue": "98"
}
}
}
```
Without changing anything, it will be displayed like this:
#### To parse this data and make it more readable, follow these steps:
1. Edit the data type for the field with your JSON data. It will be *Text* by default; change it to JSON.\
Here you can also change how the data in this column is displayed within this field – as either text or as fields.
2. Create a new Computed Field with the data you want
1. Click *Add computed column* in the table menu on the right
2. Pass the correct value to your field:\
\- Click the *ƒx Formula* button\
\- Choose the field from your table that has your JSON data\
\- Choose the JSON field and value that you need
3. Give your column an appropriate name
4. Adjust the data type for your field as necessary
3. (Optional) Hide the field with the JSON data by clicking on the slider next to the field name in the Table menu
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jetadmin.io/user-guide/data/computed-fields/formulas/parse-json-fields.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.gif?alt=media&token=be52afd2-3d50-44fe-94a9-8f7508b7d1c3)
.gif?alt=media&token=b6bc075c-9cff-48c5-94c5-f2022f318608)
.gif?alt=media&token=ad6f5548-ab56-46cc-92bc-c1a758d31b11)