Concerns: Vision/Vision Management Site/Vision Database

User: User Management Site


- Installation Futurama Vision Management Site

- Installation Futurama Vision Database


Description how to import data into Futurama Vision.


This article will describe how to import data into Futurama Vision. There are several methods to import data into Futurama Vision. The way how to import data using one of these methods is described below.

Process description

The process of importing data into Futurama Vision consists of two steps:

1. First off, the data is being imported into an intermediate table Imported DataRecords (see the related links for different options to achieve step 1).

2. After that, a RecordSet is imported into a Futurama Vision application (menu: General > import policies) or by calling the webservice with MethodName CopyImportedRecordSetToPolicySet in the service ImportUsers.svc.

The result of step 1 is a recordset with your imported data. How to import data into a Futurama Vision application is described in Further processing of data into Futurama Vision.

Required data

When records are imported into Futurama Vision, a Recordset is created. This ImportedRecordSet consists of several member records. In each record (personal) information of the specific member is saved. In the importing process there are several parameters relevant. Depending on the importing method this data will be automatically filled, or it needs to be filled in by you, the user. Below is an overview of the relevant paramaters to be filled in at the moment of importing. The way these parameters can be filled is described in the chapters where the different importing methods are described.

Set name

A set of records was called a Dataset until Futurama 18.11. This name was confusing, a set of DataItems was also called a DataSet. Therefore we renamed a DataSet to a RecordSet

The name of the recordset has to be specified. Each record with the same recordset name will be included in this recordset. For the further processing of the imported data you have to select a recordset to describe which data you want to import.

Policy XML

The policy data of each member record has to be in XML-format. This policy XML will be saved in Futurama Vision.


The PersonKey is the unique identifier of each person, e.g. the social security number.. A person can have one or more PolicyKeys (see below)


A person can have one or more PolicyKeys. Suppose you are an insurer, and you each of your clients does have a couple of policies. In that case the clients are identified by the PersonKey, and the policies of this client are identified by the PolicyKey.


It is possible to link a RecordSet to a ProductGroup. Afterwards the RecordSet can only be read and selected for further use in the Management Site by users of the Management Site that are part of the linked ProductGroup. See the security section for a explanation of defining roles in the Management Site.

Encryption keys

Futurama vision can be configured to encrypt sensitive data. When importing data into an encrypted App, you need to provide the correct encryption keys/salt combination during import step 1. Also see the paragraph Importing data in an Encrypted App below.

Import methods

Futurama Vision supports various methods of importing data:

1. By using a webservice,

2. By uploading a zip-file of member files from the Vision Management Site,

3. By using the Futurama Vision Batch console application.

Overview imported recordsets

After importing a recordset, information regarding the imported recordset can be viewed in the Futurama Vision Management Site. In this paragraph will be explained how to see, check and remove imported recordsets. In the Futurama Vision Management Site consult the subpage 'Overview imported recordsets' of the menu 'Management'. At this page you can see all the imported recordsets. Mentioned below the information you can consult for each of the recordsets.


This is the name of the recordset.

# records

The number of records contained in the recordset.


Default value is unspecified. Only relevant in the specific case of importing data for the Dutch 'Pensioenregister'. 


A recordset can be designated to a ProductGroup by the person who imported the recordset. The recordset can only be used for further processing by users of the Vision Management Site who do have the permission to consult this ProductGroup.

Removing a recordset

In case you want to delete all the rows of a recordset, press the X button in the column 'Remove' belonging to the specific recordset. Note that a recordset can be removed after it is used for further processing. After that the recordset is allready used, and will only act as a backup.

Viewing the content of a recordset

You can download a list of hashcodes of a recordset as a XML-file. Hashcodes represent the content of a XML-file, and are used to check if the imported recordsets are the same as the original recordset. This is done in the following way:

  • Within your own application, you can create a list of hashcodes. Within Futurama this can be done with the function CalculateXmlHashcode. The method of calculation for the hashcode is done by the industrial standard of the MD5 function.
  • On this range of hashcodes it is also possible to create a cumulative hashcode, by concatenating the previously mentioned hashcodes (This can be done with the ConcatenateBase64 function in Futurama), after which it is possible to create another MD5 hashcode (by using the CalculateBase64Hashcode function in Futurama). Note that it is important to pay attention to the order while concatenating. In Futurama Vision the hashcodes are concatenated according to alphabetical order of the PersonKeys.
  • After importing the datasets to Futurama Vision, you can download a list of hashcodes from the overview of this page.
  • The two lists can now be compared to one another. If the cumulatieve hashcodes are identical, then the datasets are also identical. In case they are not identical, then the hashcodes for each separate row should be compared to one another.

Import encrypted data

As described in paragraph process description, each import is a two step process. When dealing with encryption, before even starting the two steps your need to configure encryption in this App. See Futurama Vision – Data for more info how to do that.

During the import step 1, you need to provide the key/salt combinations (keyvalue specified in config) of the App you’re planning to import the data into.

The xml has to be pre-encrypted using this key-salt combination. Futurama Vision uses the Rijndael Encryption method. Encryption with the Rijndael Encryption method can be done using the Futurama formula EncryptXML

See Futurama Vision – Data for the appropriate key/salt combinations.

Related Topics

- Importing by webservice: description how to import data into Futurama Vision by using a webservice

- Importing from a zip-file: description how to import data into Futurama Vision by reading a zip-file

- Importing with Futurama Vision Batch: description how to import data in Futurama Vision using the Futurama Vision Batch

- Futurama Vision – Data : Information on Vision data, and the encryption of it

- EncryptXML: Futurama formula to encrypt XML by using the Rijndael Encryption method


If you have any questions about this subject or if you want to provide us feedback please send us an e-mail.

Updated: 2018-11-05