> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/es/releases/old/3-10-6.md).

# 3.10.6

Fecha de lanzamiento: 24 de mayo de 2022

## **Gerente de tienda y gerente central**

### Exportar informes activos a CSV

A partir de la versión 3.10.6, cuando abra un Informe activo y haga clic en **Exportar a Excel**, uno de los formatos de archivo que puede seleccionar es CSV.

## **Administrador de la tienda**

### Ejecute el archivo ejecutable Forzar instalación de tablas desde la línea de comandos

A partir de la versión 3.10.6, puede ejecutar **Forzar instalación de tablas** como un archivo ejecutable desde la línea de comandos. Esto le permite actualizar o reparar la base de datos de la tienda sin abrir Store Administrator o Store Manager.

Para usar el **Forzar instalación de tablas** archivo ejecutable, abra una línea de comandos e introduzca lo siguiente:

`"C:\Program Files(x86)\Retail Hero\RMH Store Manager\ForceInstallTables.exe" & exit /b`

El archivo ejecutable muestra un mensaje de éxito o de error. Los resultados detallados se guardan en un registro almacenado en la siguiente carpeta: **C:\ProgramData\RetailHero\RMH Store Manager\Force Install Tables**.


---

# 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.rmhpos.com/es/releases/old/3-10-6.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.