> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/analyze-with-dashboards/custom-explores/creating-custom-fields.md).
# Creating custom fields
### Introduction
You can create new ad hoc custom dimensions and measures in any explore using custom fields. This page discusses creating and using custom fields to enhance your data analysis.
### What are custom fields?
You can create and utilize ad hoc fields for richer data analysis. This is done by creating custom measures, dimensions, and table calculations and using custom groupings to narrow down data to match specific conditions.
### Filtering with a custom field
Suppose we retrieve all orders created on the 10th of each month this current year and see the associated order numbers and created date.
Click on Explore --> Orders, expand the Filters section, and click the Custom checkbox in the upper right.
When you start typing, Chord Analytics prompts you with operators, functions, and field names that you might want to use in your filters business logic. You can also see that when you hover over the function you are typing, Chord Analytics will tell what these functions, operators, and field names do.
Type in **extract\_days(${x\_fct\_trans\_orders.order\_created\_at\_date}) = 10**
Click on Visualization and click Columns
On the Explore click Order Number to include it to your report along with any Order Created Date
Click on Order Created Date again and click Filter By field icon
Order Number
Order Created Date
Click Run
You can see all created orders on the 10th of each month for this current year
Orders created every 10th of the month
{% hint style="info" %}
This [document](https://cloud.google.com/looker/docs/functions-and-operators) will further describe the functions available
{% endhint %}
You can also add the custom filters to your custom field
Click Custom Fields and click Add
Add Custom Fields
Select Dimension and paste the function used above **extract\_days(${x\_fct\_trans\_orders.order\_created\_at\_date}) = 10**
Provide the Custom Dimension a Name and click Save
You've just created and saved a custom dimension field!
### What are measure and dimension fields?
You can use Dimensions to categorize, segment, and reveal the details in your data. Dimensions affect the level of detail in the view. Measures contain numeric, quantitative values that you can measure. Dimensions include qualitative values (names, dates, or geographical data).
A **measure** is a field that can be aggregated in some way, such as a sum or an average. Think of it as something that can be collected, counted, or combined in some way to return a single value
We saw above an example of a Custom Dimension with retrieving Orders every 10th of the month. An example of a **Measure** would be if you wanted to know the average count of Product in your customers' cart
Custom Measure
{% hint style="info" %}
For more information about Custom fields and Measure Vs Dimension fields please refer to [Chord Analytics documentation](https://cloud.google.com/looker/docs/custom-fields)
{% endhint %}
{% hint style="success" %}
if you have any questions or need help, please reach out to us at
{% endhint %}
---
# 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.chord.co/analyze-with-dashboards/custom-explores/creating-custom-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.
