Example: If you selected to import Export templates only in the Data Import window, the only Export templates that do not exist in the target study are imported. For example, if the source trial group has Export templates All Forms, All Groups and SDTM while the target trial group has All Forms and All Groups, only the SDTM Export template is created. There is an informational dialog at the end which lists the Export templates that were ignored.
The import creates each export template in turn, but does not initially attempt to resolve data sources since they may be based on reusable domains that were not yet created.
The import then attempts to resolve each data source in each domain in each export template. This is done by building the data source path (e.g., [DEMOG][DM01][AGE]) from the incoming XML and locating the exact same path in the new trial group. If the path is found, the data source is re-established. If the path is not found, the data source is not created and the variable in the expression sets to NULL plus the text “Not mapped” and the original data source in comments. (You can view the export variables are not mapped in TrialBuilder via Reports > Export Variables Not Mapped Report.)
Example:
The above reference would turn into:
/* Not mapped [DEMOG][DM01][AGE] */ NULL
This is for JUST the unresolved part of the expression, for example:
CASE [PKTPT]
WHEN ‘0.5 Hours’ THEN 1
WHEN ‘1 Hour’ THEN 2
WHEN ‘2 Hours’ THEN 3
WHEN ‘2.5 Hours’ THEN 4
WHEN ‘3 Hours’ THEN 5
WHEN ‘4 Hour’s THEN 6
WHEN ‘8 Hours’ THEN 7
WHEN ’12 Hours’ THEN 8
WHEN ’24 Hours’ THEN 9
WHEN ’36 Hours’ THEN 10
END
If the system cannot determine an item to map the source to, it will replace the source Item with a NULL string. In this example it would replace PKTPT with /* Not mapped [PKTPT] */ NULL.
This replacement generates valid SQL code so that the Export can still be generated without errors.
The SDTM mappings are the same SDTM version as specified in the XML.
If the target database already contains a ProScriptFunction of the same name as one being used in the export template, the imported function is renamed as “[function name]_Imported”.
References for trial, site, and patient objects automatically get resolved to the first object of the same type in the target database. The visit is selected as the first in the schedule containing that form. For example, if the target database has Patient Type A and Patient Type B defined, references in the imported template reference A.
For missing references, the path only shows from the form level down and is separated by periods instead of brackets (brackets cause issues for the query builder), for example: /* Not Mapped DEMOG.DM.AGE */