> For the complete documentation index, see [llms.txt](https://help.accentuate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.accentuate.io/help/faq/why-cant-i-name-my-field-first-last-or-size.md).

# Why can't I name my field "first", "last" or "size"?

Over time, we have found that using the metafield names "first", "last" and "size" is problematic. These names also exist as Liquid filters in Shopify and can be used as a dot notation - see for example: <https://shopify.github.io/liquid/filters/size/>\
\
Using this construct in Liquid:

```liquid
{{ product.metafields.bundle.size }}
```

can potentially mean any of these:

1. The value of the "bundle.size" metafield
2. The length of the namespace name itself - "bundle" = 6
3. The number of metafields within the namespace "bundle"

To minimize any issues, ACF blocks you from using these custom field names with problematic ambiguous meanings in Liquid.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.accentuate.io/help/faq/why-cant-i-name-my-field-first-last-or-size.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.