| | Importación/exportación de versionesYou can copy data from one system or company to another. These
sessions provide the functionality: - Export Version Dump (tgbrg1235m000).
- Import Version Dump (tgbrg1245m000)
Exportar volcado de versión (tgbrg1235m000) Use the Exportar volcado de versión (tgbrg1235m000) session to export
version data to an ASCII file. You can use the ASCII file for these
purposes: - To copy data from one system or company to another system or
company.
- To translate descriptions and texts.
- To convert data from the current LN release to a
previous release, such as Baan IVc.
- Create backups of your DEM data.
All data in the selected version that falls within the selection
parameters will be exported. To import data exported with the current session,
use the Importar volcado de versión (tgbrg1245m000) session. To make an export dump, complete the following
steps: - In the Versión field, select a version that provides the
model items you want to export.
- To export data from versions from which the version you have
selected is derived, select the Incluir versiones anteriores check box.
- In the Archivo field, specify a file where the ASCII file must
be written to.
- On the successive tabs, select the ranges of model items you
want to export.
- Click Exportar
| Key fields for the Exportar volcado de versión (tgbrg1235m000) session | | Field | Description | | Comprimir | Si esta casilla de verificación está seleccionada, the ASCII file is stored
in a compressed format. You cannot read the file in UNIX VI or MS Notepad. The
file will be automatically decompressed when you import the file with the Importar volcado de versión (tgbrg1245m000) session. | | Convertir a | Select the Infor ERP release to which you want to
convert the component information. If the export file is for use within the
same LN release, you
can select Sin conversión. | | Incluir comentarios de traducción | Si esta casilla de verificación está seleccionada,, explanatory information
is inserted in the export file to identify the model items. | | Excluir formato de texto enriquecido (rtf) | Si esta casilla de verificación está seleccionada,, repository Help or
model specific Help stored in rtf format is not exported. | | Ocultar sesión | Si esta casilla de verificación está seleccionada,, the session window is
hidden and a progress window appears when you click Exportar. | | Exportar elementos de modelo usados en modelos empresariales | Select a method to retrieve the model items used in
the business models: - No: Option is not active
- Manual:
Select a range for used model items. Only the model items that fall within the
selection ranges and linked to a business model of the selected version are
exported.
- Automático: Exports all the model items used in a
business model of the selected version.
| | Exportar elementos de modelo usados en repositorio | Select a method to retrieve the model items used in
the repository. |
Importar volcado de versión (tgbrg1245m000) Use the Importar volcado de versión (tgbrg1245m000) session for the following purposes: - To copy data from one system or company to another system or
company.
- To import translated descriptions and texts.
- To import a backup of DEM data.
Import files are created with the Exportar volcado de versión (tgbrg1235m000) session. If the source version, created with the Exportar volcado de versión (tgbrg1235m000) session, is different from the version into which you
want to import the data, you must select the Importar elementos de modelo en versión diferente check
box. When the data is being imported, LN checks whether the
version to be imported already exists in the target system or company. If the
version does not exist, LN will ask if the version must be created. If the import file contains data from derived-from-versions, the
file was exported with the Incluir versiones anteriores check box selected in the Exportar volcado de versión (tgbrg1235m000) session. Therefore, this structure must also exist in
the system or company into which the file is imported. If the import file
contains data from derived-from-versions, and this data is imported into a
different version than the version it was originally exported from, the DEM
data versions are purged into one import version. If an import file is exported from an older DEM software
version, the DEM data is automatically converted to the new DEM data
format. If you import Baan IVc DEM data, you are prompted to specify the LN component to which
the ERP session must be linked. This component, together with its applications,
must be available. If an imported version is protected with a license, you need
to enter the license registration. If the data in the file is not correct, a log file will be
printed with the errors and the line number in the file. Ejemplo - A reference does not exist
- A code or description is too long
- A table field does not exist
To import a version dump: - In the Archivo field, specify the path where the version dump is
located and from where you want to import it.
- On the successive tabs, select the ranges of model items you
want to import.
- Click Importar
| Key fields for the Importar volcado de versión (tgbrg1245m000) session | | Field | Description |
|---|
| Importar elementos de modelo en versión diferente | Si esta casilla de verificación está seleccionada,, the data must be
imported into a target version that differs from the source version from where
the dump was created. Specify the target version in the Import into
Version field. | | Verificar integridad de datos | Si esta casilla de verificación está seleccionada,, the information in the
import file is checked for: - All references from a model item must exist.
- All descriptions are checked to ensure they still
comply with the domain definition on the target system; if not, they are
adjusted to the new domain.
| | Listar errores | Si esta casilla de verificación está seleccionada,, errors that occur
during the import are printed. | | Ocultar sesión | Si esta casilla de verificación está seleccionada,, the session window is
hidden and a progress window appears when you click Importar. |
Import Language-Dependent Data from XML - Wizard (ttadv8920m000) To import XML files with language-dependent components into
the data dictionary, use the Import Language-Dependent Data from XML - Wizard (ttadv8920m000) session.
When you import the language-dependent components, Tools will take the
following actions: - Compile the imported labels
- Convert imported domains to run-time
- Convert the imported system overhead to run-time
After the import, the imported components are ready for
immediate use at run-time. In Tools, you can define multiple labels with the same code,
which have different heights, and lengths. By default, Tools displays the longest label defined for the
label code of a software component. If an imported label is shorter than any existing labels with
the same code in the VRC, the existing older label displays on the software
component. To ensure the imported labels display for your VRC’s software
components, select the Remove Existing Label Variants check box in this session. Nota If an error occurs during the import process, Tools does not
compile the labels. However, to compile these labels after the import process,
use the Compile Labels (ttadv1243m000) session. For more specific information, refer to the online help of this
session. | |