> For the complete documentation index, see [llms.txt](https://docs.antsomi.com/cdp-365-user-guide-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antsomi.com/cdp-365-user-guide-en/use-cases/data-hub/business-objects/how-to-create-a-collection.md).
# How to create a Collection
## Use case:
I want to create a Collection of Products that contains all the jackets for Men and Women
## Steps:
1. Hover your mouse over **Data** on the left hand side menu, select **Data Object.**
Choose the **Product** object, and select the **Collections** tab
In the Collection tab, click 
2\. Configure Collection
* Collection Name: Jackets
* Description: Jacket Collection
* Include item that:
* Click 
* Choose **Have Attribute**
* Enter condition
* Attribute: Category level 2
* Condition: match any of
* Field: Jackets
* Collection Item:
* Sort collection, then get top of 100 item(s)
* Sort by Name, Sort order Ascending
* Update Collection: Static Collection - no update
* Notification Setup: Notify when the computation fails by **sending an Email and pushing a notification**
* Estimated Results (optional): click **Forecast** at the right hand side of the screen
3\. Click **Save**
{% embed url="" %}
---
# 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://docs.antsomi.com/cdp-365-user-guide-en/use-cases/data-hub/business-objects/how-to-create-a-collection.md?ask=&goal=
```
`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.
