The file should have a header row which defines the properties that are going to be imported, and then one row for each object of the Biskit Type. Use the Search page or the Bakery to find the names for the properties. All the fields need to be comma separated.

 

To modify the value of a property that is from a component biskit,  values to all the properties on that component must be provided. Any properties not mentioned will be attempted to be set to null. If this fails then an error will occur.

Eg, When importing users and setting a new value for userIdentity.authenticationMethod, then a value for userIdentity.loginName must also be set.

If a new value for userIdentity.authenticationMethod is set and  a new value for userIdentity.loginName is not set, then the userIdentity.loginName will be set to null.

 

A property that is used to identify the biskit to be updated can itself be updated. For example, when importing users, users could be identified by their email property (if it's unique) and the import could also modify that email property. To do this, two email columns in the CSV file are required.

 

i.e.

email,email

tim@conaptic.com,timb@conaptic.com

 

The first column would then be the key property to identify the user to be changed and the second column would be the new value of the email property.

 

Use the following options Key: and Ignore: (typed before the property name) to pre select the properties that will be key fields or fields to be ignored.

Example File For Importing A User

 

 

The User record that will be created from this file:

 

 

Notice the order of the properties does not matter. Depending on how the system is configured password may be a compulsory property and may have a minimum number of characters and/or a combination of alphanumerics.

Example File For Importing A Resource

 

 

The Resource record that will be created from this file:

 

Example File For Importing A Project

 

 

The Project record that will be created from this file:

 

 

Projects have other information attached to them but they are stored in different Biskit Types. These are used to store the Project Resource Settings, Users and Project Groups properties. In order to import this information, first import the project information and then import each of the other three Biskit Types one after another.

 

For example importing the Project Resource Settings for the above project:

 

 

Example File For Importing A Time Template

 

 

The Template record that will be created from this file:

 

 

To import repeat Time Templates see below for additional information about importing repeat bookings.

Example File For Importing Two Bookings

 

 

The Booking record that will be created from the first import line in this file is:

 

 

 

When importing repeat bookings the repeat sub Biskit Type for the repeat booking needs to be defined as well as all the properties defined for that Biskit Type and all the properties of the parent Biskit Type Repeat. Any property not defined will have its value set to null.