The "Data view" menu helps you view database data for projects and export data extracted by robots. You can also use it to see database tables created from types using Design Studio or Management Console.

At the top of the menu, in the Projects drop-down list, you can select the project with the data to display. On the left side, you can see the Database navigation tree displaying database mappings defined for the selected project.

If no database connection is established, or if tables have not been created for a database, the database mapping name under the navigation tree is not active (not expandable).

When you click a database mapping name, the tree is expanded, and you can see the various tables contained in the database. When you select a table, the type data is displayed in the right pane, including the names of types, robots associated with those types, and types attributes. You can copy data directly from the table. You can select the columns to display for a database table using the menu icon on the right.

Once the data is loaded, a number of filters become available that work in the same way as the filters in the Log view. For example, you can filter by the following conditions: Contains, Not contains, One of, Starts with, and so on. Binary and longtext attributes are not filterable.

Export data

Above the data grid, in the Export to drop-down list, you can select the format to export data extracted by robots: XML, CSV, or EXCEL.

To see previous exports and/or download them again, click Exports .

By default, the following information is displayed for each export.

The exports are automatically deleted the next time the Management Console is started. The oldest exports are deleted when the number of exports exceeds 100. There is no limit to the number of rows you can export to CSV or XML, but Excel files are limited to 10000 records, to prevent the system from running out of memory.

The list of schemas/catalogs available under each database in the navigation tree is controlled by the permissions of the user whose credentials are used in the cluster settings database configuration.