> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/grid-microchart-guide/creating-a-micro-chart.md).
# Creating a micro chart
### Using the grid to create a Micro Chart
From the 4.1 version of Vitara charts, trendlines feature is added in the Grid chart. With this feature, we can convert the Grid chart into Micro chart.
#### Inputs
**Attributes required:** 2 or more\
**Metrics required:** 1 or more
Follow the below procedure to convert the Grid chart into Micro chart.\
**Step 1:**\
Create a Grid chart with 2 or more attributes and minimum of 1 metric. For example, we have a grid chart created with 2 attributes and 3 metrics. See the screenshot
**Step 2:**\
Group by the attribute ‘Year’. In the Micro chart, we have two drop zones for attributes called Category axis and Trend By. In this example, ‘year’ will be the category axis attribute and ‘Category’ will be the Trend By attribute.\
See the screenshot which shows the year attribute in grouped state.
**Step 3:**\
Now we will apply 3 different trend lines for the 3 different metrics. To know about trend lines [click here](https://docs.vitaracharts.com/grid-microchart-guide/trend-lines)\
See the screenshot which shows the trendlines applied.
**Step 4:**\
Finally, hide the Grid dropzones using below steps
1. Open property editor > Appearance tab.
2. Set the ‘Grouping/Pivoting dropzone’ to hide\
See the screenshot below with hidden Grid dropzones.
If you have noticed the above image, the grid dropzones are hidden. Just compare this screenshot with the screenshot in step 3. And the Grid chart is now converted to Micro chart
For detailed information on configuring Trendline settings, refer to the [Trendline](/grid-microchart-guide/trend-lines.md) documentation
---
# 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.vitaracharts.com/grid-microchart-guide/creating-a-micro-chart.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.
