Excel Import

With the Excel Importer, you can easily and efficiently import your data into Ardoq. The import functionality supports .xls, .xlsx, .xslm, and .csv formats.

This article assumes that you are familiar with the basic concepts in Ardoq. If you are new to Ardoq this is a great place to start.

You can download the sample Excel file used in this article here.

What does it do?

When you're importing new data from Excel, you need to first configure a mapping. Conceptually you're defining how to translate a tabular data set (Excel) to a graph representation (Ardoq), which can be a bit complicated. To help with this, the importer will guide you through the process and also show you a preview of the resulting model.

A mapping allows you to:

  • Flexibly generate Ardoq models based on your Excel data
  • Define which workspaces a sheet will import data into
  • Map columns in Excel to either descriptions, component types, fields or tags in Ardoq
  • Dry-run to verify that your Excel data is consistent with your mappings (i.e. check that the data type is correct with your field mapping)

You can also use Excel to update existing data in Ardoq. This is a great option for doing bulk updates/changes.

Setting up your spreadsheet

Dowload the example file for details on supported mappings.

Import you data

Use the left menu item "Import your data" to access the Importer. 

Select Excel from the Import and Integrations landing page and upload your file.

After you have uploaded your file, you will see the sheet overview where you can define, map and modify. For each worksheet, you need to make a selection of components or references and then click configure button to define the structure and mapping. The sheet overview will provide you with feedback on your selection of components and references, the status of the configuration and errors after you've done a test run.

If you would like Ardoq to ignore specific worksheets, don’t make any selection for components or references. The Reset button will clear your selection.

Component Mapping

First find the workspace or create a new workspace for these components. Then select the column headers to start mapping data and defining hierarchy.

Here is an example where you can see the structure and component mapping. 

Reference Mapping

For references, select the source and target workspaces the references will point between (they can be in the same workspace). Remember. If there are no matching components in the source or target workspaces, you will not be able to import.

Dry-run and Importing Data

After you have defined and mapped worksheets, you can test run to review and check for errors. Click the Test Run button to see the summary.

If you have structural or validation errors, you will not be able to import so you’ll need to make changes and then upload again. 

After you have made changes, uploaded, tested and are error free you will receive feedback that you are ready for import.

Click the Import button and wait for Ardoq to confirm the workspaces that have been updated.

Considerations and constraints

Mapping inconveniences 

Be aware that if you add or rearrange the order of worksheets in the file, Ardoq will not be able to preserve your structure or mapping. This is a limitation we'll address in the next iteration.

If you rename your file, Ardoq will not remember your mapping.

Ardoq will store you configuration within you session, but you cannot store you mapping between session. This is also being addressed in the next iteration.

Supported models

The Excel uploader supports flexible models. That said, we recommend keeping the models as simple as possible, in order to ease communication and make them understandable to others.

Reserved Field Labels

Some field names are reserved in Ardoq. If you are trying to map a field using a reserved field name, you'll get an exception and have to re-name the field.

Workspace permission issues

Remember that the Excel importer is subject to permissions checks. That means you cannot import into workspace you only have read permissions to.

Did this answer your question?