> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/enitites/batch-entity.md).
# Batch Entity
### **Overview**
The Batch Entity Editor allows users to view and update multiple entities directly from a single screen. Entities are organized under separate tabs such as Members, Tables, and Customers. Users can search for entities, edit the displayed details, and save the changes without opening each entity individually.
### **Screen Elements**
| **Screen Element** | **Description** |
| ------------------ | --------------------------------------------------------------------------- |
| Members | Displays the available member entities for viewing and editing. |
| Tables | Displays the available table entities for viewing and editing. |
| Customers | Displays the available customer entities for viewing and editing. |
| Name | Displays the name or identifier of the entity. |
| Address | Displays the address associated with the entity, where applicable. |
| TaxId | Displays the tax identification details for the customer, where applicable. |
| Test | Displays the customer name details, where applicable. |
| CompanyName | Displays the company name associated with the customer, where applicable. |
| Email | Displays the email address associated with the customer, where applicable. |
| Search | Allows users to search for a specific entity. |
| Save Changes | Saves the changes made to the entities. |
| Close | Closes the Batch Entity Editor. |
### **Working**
#### **Edit an Entity**
1. From the Batch Entity Editor, select the required entity type, such as "Members", "Tables", or "Customers".
2. Locate the required entity from the list.
3. Double-click the required entity field to make it editable.
4. Update the required details.
5. Select "Save Changes" to save the updates.
#### **Search for an Entity**
1. Select the required entity type.
2. Enter the entity name or relevant details in "Search".
3. Review the filtered results.
#### **Switch Entity Type**
1. Select "Members", "Tables", or "Customers" to view the corresponding entities.
2. Select the required entity and update the details as needed.
### **Use Case**
* Update multiple member details from a single screen.
* Modify table names or details without opening individual entities.
* Update customer information such as name, address, company name, or email.
* Search for a specific entity when the list contains multiple records.
* Switch between Members, Tables, and Customers for different entity types.
* Make quick changes directly within the entity list.
* Save multiple updates together using "Save Changes".
* Manage entity information efficiently from a centralized screen.
### **Notes**
* Existing entity details can be edited by double-clicking the required field.
* Select "Save Changes" after making updates.
* The available fields may vary depending on the selected entity type.
* Use the "Search" option to quickly locate an entity.
---
# 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://help.rbsgo.com/dineplan/backoffice/enitites/batch-entity.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.
.png?alt=media)
