---
title: Converting Files
slug: ryze/converting-files
description: Learn how to convert various types of study metadata files into different formats using Formedix's services. This document provides step-by-step instructions for converting Veeva Vault, Medidata Rave ALS, Oracle InForm, Define-XML, Excel, and SAS XPT file
createdAt: 2023-08-31T12:28:42.732Z
---

## Convert Veeva Vault to ryze

The Veeva converter can be used to convert a Veeva Vault Study design specification (SDS) into an ODM file. You can then upload the ODM file into your repository. The source file must be saved as type 'XML Spreadsheet 2003'.

The Veeva converter can be used with the [Veeva Plugin](https://docs.formedix.com/ryze/veeva-plugin-guide) to import metadata from Veeva Vault EDC.&#x20;

## Convert Medidata Rave to ryze

:::Iframe{code="<div style=&#x22;padding:57.02% 0 0 0;position:relative;&#x22;><iframe src=&#x22;https://player.vimeo.com/video/601119124?h=a51ab4dbf6&#x26;amp;badge=0&#x26;amp;autopause=0&#x26;amp;player_id=0&#x26;amp;app_id=58479&#x22; frameborder=&#x22;0&#x22; allow=&#x22;autoplay; fullscreen; picture-in-picture&#x22; style=&#x22;position:absolute;top:0;left:0;width:100%;height:100%;&#x22; title=&#x22;Converting Rave ALS to ODM and Importing Content&#x22;></iframe></div><script src=&#x22;https://player.vimeo.com/api/player.js&#x22;></script>"}

:::

Use this service to convert study metadata held in a Rave ALS (Architect Loader Spreadsheet) file into a Formedix ryze file.

- The ALS source file must always be in the 'XML Spreadsheet 2003'. format and can have .xml or .xls file extensions.
- This service may take several hours to complete for large studies.

 To convert a Rave ALS file to a Formedix ryze file:

1. Select **Services** from the **Navigation** bar and open the **Services** tab.
2. Select **Convert Medidata Rave to ryze**.
3. [Upload the source file](https://docs.formedix.com/ryze/on-demand-services) for the service and select **Convert**. The file is validated before conversion to check it's a valid file.
4. Select **Downloads** from the **Navigation** bar.
5. Check the conversion status:
   - **Completed&#x20;**- This confirms that no problems were found with the input file and the output file complies with the ODM standard.
   - **Completed with issues&#x20;**- Read the report and decide if you want to fix the source file and try again.
   - **Failed&#x20;**- Read the report and fix any issues before trying again.
6. To download the file, click the **download icon**.

## Convert Oracle InForm to ryze

Use this service to convert study metadata, held in two Oracle InForm files, into Formedix ryze files:

- CSML source file from Central Designer Client (mandatory)
- Units XML file from Central Designer Administrator (not mandatory unless study contains measurement units)
  - You must name the units XML file **'Unit Definitions.xml'**.
  - If you use another name, the units will not be converted and the ODM file will not contain units.

 To convert an Oracle InForm CMSL file to a Formedix ryzefile:

1. Select **Services** from the **Navigation** bar and open the **Services** tab.
2. Select **Convert Oracle InForm to ryze**.
3. Select **Choose** next to \* File and browse to select a CSML file. The file is validated before conversion to check it's a valid file.
4. (Optional) Select **Choose** next to XML File and browse to select an XML file if your study contains measurement units.
5. Select **Convert**.
6. Select **Downloads** from the **Navigation** bar.
7. Check the conversion status:
   - Completed- This confirms that no problems were found with the input file/s and the output file complies with the ODM standard.
   - Completed with issues. Read the report and decide if you want to fix the source file and try again.
   - Failed - Read the report and fix any issues before trying again.
8. To download the file, click the **download icon**.

## Convert Define‑XML 1.0 to Define‑XML 2.0

Use this service to convert a Define-XML 1.0 file to a Define-XML 2.0 file.

  The converted Define-XML 2.0 may require the addition of further information before it can be used a part of a submission.

 To convert a Define-XML 1.0 file to a Define-XML 2.0 file:

1. Select **Services** from the **Navigation** bar.
2. Select **Convert Define-XML 1.0 to Define-XML 2.0**.
3. [Upload the source file](https://docs.formedix.com/ryze/on-demand-services) for the service and select **Convert**.
4. Select **Downloads** from the **Navigation** bar:
   - Completed - This confirms that the converted file complies with the Define‑XML 2.0 standard.
   - Completed with issues - Read the report and decide if you want to fix the source file and try again.
   - Failed - Read the report and fix any issues before trying again.
5. Select **Download**.

## Convert Excel to Define‑XML 2.0

Use this service to convert an Excel spreadsheet file containing dataset metadata to a Define-XML 2.0 file.

 To convert the Excel file to Define‑XML 2.0:

1. Select **Services** from the **Navigation** bar.
2. Select **Convert Excel to Define-XML**.
3. Select **here** to download the Formedix template. You must use a Formedix spreadsheet template if you want to define your own code lists and value lists.
4. [Upload the source file](https://docs.formedix.com/ryze/on-demand-services) for the service and select **Convert**.
5. Select **Downloads** from the **Navigation** bar.
6. Check the conversion status:
   - Completed - This confirms that the converted file complies with the Define‑XML 2.0 standard.
   - Completed with issues - Read the report and decide if you want to fix the source file and try again.
   - Failed - Read the report and fix any issues before trying again.
7. To download the file, click the **download icon**.

## Convert SAS XPT to Define‑XML 1.0

Use this service to create a Define-XML 1.0 file from one or more SAS XPT files. This includes code lists and value lists.

You must use a Formedix spreadsheet template if you want to define your own code lists and value lists.

 To create a spreadsheet in the Formedix format:

1. Download the Formedix spreadsheet template and open within Excel.
2. Fill out the spreadsheet as described in the **Instructions** tab and then select **Save**.

Do not use the **Save as** option. The file must remain in 'XML Spreadsheet 2003' format.

To convert the file(s):

1. Select **Services** from the **Navigation** bar.
2. Select **Convert SAS XPT to Define-XML 1.0**.
3. Upload the source file and complete the following:

### Protocol identifier

An alphanumeric name that identifies the document used to define and manage the trial.

### Standard name&#x20;

Select the CDISC standard that the datasets conform to. The Define‑XML file will then be supplemented with the additional information required for this standard.

 **Generate valuelist from the data**

This option is not available if the Standard name is set to 'None'. 

Select this option to include value lists in the output Define‑XML. For example, when you select a standard, all of the variables that would typically have value lists, such as '--TESTCD', will have value lists added.

 **Generate lengths from the data**

Select this option if you want the values for the 'Length' attribute for each variable within the output Define‑XML to be generated based on the input data.

The longest data value in each column will be used for the length.

If not selected, the lengths from the XPT metadata will be used.

### Generate code lists

**None**

Select this option if no code lists are to be generated.

**Merge from file**

Select this option if you want code lists to be generated based on a spreadsheet file. A template for the spreadsheet and documentation for how to create it can be downloaded below:

::File{src="https://api.archbee.com/api/presign/Ypd1rBe_ZmYCuFegg-M36-PLpBfDS0lDj8t4FPsnyl1-20240903-135410.xml" label="excel-cl-to-def-nci-Template.xml"}

Select **Choose**, browse to the code list file and select **Open**.

**Generate from data**

Select this option if you want code lists to be generated based on the input data.

Code lists will be generated for each variable which has a code list specified in the CDISC standards.

Code list items within the code lists will be generated based on the de‑duplicated input data values.

**Merge and generate**

Select this option if you want code lists to be generated using both of the options above.

If a code list is specified for a variable in the spreadsheet and a code list is also specified for this variable in the CDISC standards, the spreadsheet code list will take precedence.

A template for the spreadsheet and documentation for how to create it can be downloaded below:

::File{src="https://api.archbee.com/api/presign/Ypd1rBe_ZmYCuFegg-M36-PLpBfDS0lDj8t4FPsnyl1-20240903-135410.xml" label="excel-cl-to-def-nci-Template.xml"}

Select **Choose**, browse to the code list file and select **Open**.

Select **Convert** and then select **Downloads** from the **Navigation** bar.

The cog icon indicates that the data upload may take a few minutes.

1. Check the conversion status:
   - Completed - This confirms that the converted file complies with the Define‑XML 1.0 standard. If a Standard name was specified, it also indicates that the Define conforms to that standard.&#x20;
   - Completed with issues - Read the report and decide if you want to fix the source files and try again.
   - Failed - Read the report and fix any issues before trying again.
2. To download the file, click the **download icon**.

## Convert SAS XPT to Define‑XML 1.0 (preview)

Use this service to generate a PDF showing the content of the Define‑XML that would be generated by the full service.

You must use a Formedix spreadsheet template if you want to define your own code lists and value lists.
