Exporting configuration data

Using the XML Export form, you can export configuration data too. This data includes:

  • Extension table definitions
  • Standard guidelines
  • Item guidelines
  • Parameter guidelines
  • Criteria for Quick search setup
  • Lookups and views
  • Validation codes
  • Grid property codes
  • Role-based templates
  • Locations
  • Script libraries
  • Dependent extension fields
  • Language elements
Note: To export data from one Optiva database for use in another Optiva database, see Using the Configuration Transporter.

Exporting profile attributes

You can also export the profile attributes using three different symbols.

  • PROFILE - exports the profile attributes that are specified for @DFLT
  • USERS - exports the profile attributes that are specified for an individual user
  • LABORATORY - exports the profile attributes that are specified for an individual lab

Exporting parameters

Now, you can use the TPIMPORT detail code to export items. This detail code exports only parameters with a value or an attribute with a value. It exports all parameters, regardless of whether they are used in the current Lab.

Consider using TPIMPORT instead of TPALL to avoid exporting extra blank rows in your XML file.

This differs from the TPALL detail code. TPALL only exports all parameters, even parameters with non-null values, from the current lab.

TPIMPORT does not export PVALUE formatted values. You can export PVALUE formatted values with the TPALL detail code.