> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/setups/setup-items/setup-items-multiple-pack-sizes/configuration-multiple-packs-sizes/configuration-options-1/do-not-allow-entry-w-o-group-selection.md).

# Do Not Allow Entry W/o Group Selection

**YouTube:** [How To Make Group Selection Mandatory While Creating a New Item in Logic ERP Software?](https://www.youtube.com/watch?v=i3Lt2dfld0Q\&t=29s)

## How To Make Group Selection Mandatory While Creating a New Item in Logic ERP Software?

In this tutorial, we will delve into an essential feature of ERP systems: implementing restrictions to prevent item creation unless a specific group has been selected. This ensures data accuracy, maintains organizational structure, and enhances overall system efficiency.

**Benefits of Group Selection:**

* **Data Consistency:** Ensures accurate categorization.
* **Improved Reporting:** Facilitates better analysis.
* **Reduced Errors:** Minimizes data entry mistakes.
* **Enhanced User Experience:** Provides clarity and organization.

### **Steps to Configure:**

* Navigate to the Setups/Setup Items and then click on "Setup Items Multiple Packs/Sizes".
* Click on Configuration
* Locate the option "Do Not Allow Entry W/o Group Selection" under the Configuration option - 1.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FcrWEd170JNfKKNQjgRDx%2FDo%20Not%20Allow%20Entry%20Wo%20Group%20Selection%20-%20Configuration.png?alt=media&amp;token=fa8327eb-1658-4ecd-8b29-3f51ee4bf49c" alt=""><figcaption><p>Click on the option to enable it as instructed.</p></figcaption></figure>

### Implement in Item Master

* **Create an Item:** Attempt creating an item without group selection to see the restriction in action.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F5gJJarhJhJS9kLD3UDAW%2FPrompt%20for%20Group%20selection.png?alt=media&amp;token=e7c2ebe7-0184-4abf-b9e9-4e0269e01834" alt=""><figcaption><p>As you can see, saving the item without selecting a group prompted the message: "Group-2 Cannot be blank... Please Check."</p></figcaption></figure>


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/setups/setup-items/setup-items-multiple-pack-sizes/configuration-multiple-packs-sizes/configuration-options-1/do-not-allow-entry-w-o-group-selection.md?ask=<question>&goal=<user_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.
