Scenario: Import data and configuration

This scenario describes BRIX import options: importing data into an app, migrating a configuration, or synchronizing users and groups with an AD/LDAP directory.

It is important to distinguish three types of import:

  • Data: App items that users work with, such as requests, vendors, products, clients, documents, and inquiries.
  • Configuration and components: System settings, including workspaces, apps, forms, business processes, pages, solutions, and modules.
  • Users and groups: Employees and user groups imported from an external AD/LDAP directory.

For example, as part of a procurement workflow scenario, you can import vendor and product directories, migrate a configured Procurement workspace, install a ready-made solution from an .e365 file, or import users and groups from AD/LDAP.

This scenario explains the overall setup logic and does not replace detailed instructions. At each step, you will find links to help articles with detailed descriptions of the steps and required parameters.

Prerequisites before configuration

Before starting an import, determine the following parameters:

  • Import object: What needs to be migrated, such as data, a configuration or its component, user accounts, or groups.
  • Target environment: Where to import the items, such as a test company, production company, or another environment.
  • Links and dependencies: Any linked data or dependencies present.
  • Access permissions: Whether access needs to be configured for objects after import.

These parameters determine the choice of migration method. Data is imported from Excel or CSV files. A configuration is migrated by exporting and importing an app, workspace, solution, or module. Users and groups are imported from AD/LDAP.

Step 1. Select the import type

The import method depends on the type of objects being migrated:

  • Data import: Used to import records into an existing app. For example, import a list of companies to populate the Vendors app.
  • Configuration import: Used to migrate settings. For example, import a configured Procurement workspace with apps and processes from a test environment into a production environment.
  • AD/LDAP import: Used to create employee user accounts and migrate user groups.

Начало примечание

Related articles:

Конец примечание

Data import path

Follow these steps to import items into an existing app from an Excel or CSV file.

Step 2. Prepare the app and file

Ensure that the target app is created in the system and that its field composition and types match the structure of the imported file.

For example, before importing vendors, verify that the Vendors app includes the Company Name, Tax ID, Contact Person, Phone, Email, and Status fields.

If data is linked to other apps, determine the import sequence in advance. Import directories and related items first, followed by the main data referencing them. For example, in the Procurement solution, populate vendor and product registers first before importing purchase requests.

Pre-import file validation checklist:

  • Matching column names and app fields.
  • Populated required fields.
  • Display format for dates and numerical values.
  • Values for drop-down list fields.
  • Links to other apps.

Начало примечание

Related articles:

  • Import data: Learn which files can be used and how to map columns to app fields.
  • Export data: Learn how to export current app data to use as a template for import.
  • System data types: Learn about available field data types.
  • App data type: Learn how to configure links to items in another app.

Конец примечание

Step 3. Import data and verify the result

Upload the prepared file on the app page and map its columns to app fields.

After the import completes, verify the following:

  • Total number of successfully imported records.
  • Populated required fields.
  • Correct recognition of data types, such as dates, numbers, and lists.
  • Active links with items in other apps.
  • Absence of duplicate records.

If some rows failed to import, fix the file or column mapping and retry the import.

Начало примечание

Related articles:

Конец примечание

Configuration import path

Follow these steps to migrate individual configuration components, such as an app, workspace, solution, or module.

Step 4. Select the object to migrate

Identify the object and select the appropriate migration tool for your task:

  • Single app: App export and import.
  • Workspace with multiple apps: Workspace export and import.
  • Linked set of components: Solution export and import using an .e365 file.
  • Extension or integration component: Module export and import.
  • Entire company settings and architecture: Configuration export and update.

For example, if you only need to migrate the Vendors app, exporting the app is sufficient. To migrate an entire procurement workflow with its workspace, apps, and processes, prepare the Procurement solution and export it to an .e365 file.

Начало примечание

Related articles:

Конец примечание

Step 5. Import the component and verify the result

Before importing, check for external dependencies, such as system workspaces, licensed products, modules, users, groups, or other objects referenced by the component being migrated.

Import the selected object into the target company. If the solution is already installed, update the solution rather than reinstalling a new package.

After importing, ensure the components are accessible in the system:

  • The workspace appears in the main menu.
  • Apps open without errors.
  • Processes are available to launch.
  • Pages and widgets function correctly.

Начало примечание

Related articles:

Конец примечание

Users and groups import path

Follow these steps to import users and groups from AD/LDAP.

This import creates users and groups in BRIX, but does not replace access permission configuration.

Step 6. Import users and groups from AD/LDAP

Configure integration parameters with the external directory and run the data import process.

After the import completes, verify the following:

  • Created accounts exist in the user directory.
  • Active status of imported employees.
  • Correct assignment of users to groups.
  • Proper execution of import and synchronization operations.

Начало примечание

Related articles:

Конец примечание

Step 7. Verify results in a production scenario

After completing any import type, perform a comprehensive verification of data and settings:

  • For data: Open several records in the app and verify links between them. For example, after importing vendors and products, create a test purchase request.
  • For a configuration or its component: Verify the primary scenario: the workspace displays, apps open, and forms and processes function correctly.
  • For users and groups: Ensure users are active, belong to the correct groups, and gain access once permissions are configured.

Начало примечание

Related articles:

Конец примечание

Workflow summary

  1. First, select the import type:

Determine what needs to be migrated: data, configuration, or users and groups.

  1. For data import:
  • Prepare the app and an Excel or CSV file.
  • Import the data.
  • Verify records, links, and duplicates.
  1. For configuration or component import:
  • Select the object to migrate: an app, workspace, solution, or module.
  • Import the configuration into the target company.
  • Verify dependencies and the operation of migrated components.
  • If the solution is already installed, update the solution.
  1. For user and group import:
  • Configure import from the AD/LDAP directory.
  • Verify users, groups, and synchronization operations.
  • Configure user access permissions after import.
guide-users.html how_to_create_an_app.html