Dataset Conversion

dataset conversions can be run for datasets or asset groups you can upload a dataset to be used in a dataset conversion or choose source and target datasets from your existing content to run a dataset conversion you must define a mapping specification using the dataset mapper plugin, and run a conversion task data conversion api resources are available with the formedix web services api and can be used to automate conversions for more information, see the docid\ kmqgcz j0qe6 a9qvevuz upload datasets allows you to upload a dataset in a specific file format supported file formats include sas transport xpt dataset xml delimited text format csv zip file containing any of the above you can also view the data associated with uploaded datasets run conversion conversions can be run at the asset group level or at the dataset level you must have the dataset mapper plugin enabled and specify a mapping source in plugin properties see the docid\ dkmua9njlzyseskhiiz0d for more information on mapping download datasets allows you to download the current dataset view as a sas transport xpt, dataset xml, or delimited text format csv file data cleaning data cleaning can be used to replace characters in data sources data cleaning operations are applied to data that is pulled from an integration or data that is uploaded directly to ryze for example, if your source data has invalid characters that you need to change on import characters must be entered in hexadecimal format if a replacement character isn’t specified in the target input, then it is replaced with 20 (blank space) p21e validations you can run p21 enterprise validations on sdtm and send datasets these validations run automatically after a dataset conversion task by combining ryze apis and p21 ecli, you can automate the flow of data and streamline processes to enable a ryze p21e connection, contact your certara customer success or support representative once you have the connection enabled, you can convert and validate datasets directly from your repository the option to validate your datasets in p21e appears as a checkbox before you run the conversion task this checkbox is checked by default for new conversion tasks after running a successful conversion task, the p21e validation results url is displayed you may need to refresh ryze after running the conversion click the url to open the validation overview in p21e ryze passes the study program, study label and asset group label to p21e if these don't exist in p21e, a new data package is created external standards if an external standard is set, then the validation is run against the specified standard and version if no external standard is set, it defaults to the latest version for example, sdtm ig 3 4 or send ig 3 1 define xml when you run p21 validations, a define xml file is generated in ryze and passed to p21e depending on the version, one of the following define xml files is generated define xml 2 1 with cdisc stylesheet define xml 2 0 with cdisc stylesheet the define xml version is specified in standard/study properties acrf annotated crfs (acrfs) can be passed to p21e when you run the conversion task, the annotated “blank crfs pdf" visualization is automatically generated by default and passed to p21e to include acrfs, the crf plugin must be enabled and plugin properties > crf properties > annotations set to "show" which data acquisition asset group is used? the following logic is used to generate the annotated crf if this is not suitable, generate the acrf manually if no asset groups have the crf plugin enabled, the acrf is not passed to p21e if one asset group has the crf plugin enabled, the visualization is generated from that asset group if multiple asset groups have the crf plugin enabled select the one that has the most forms if there are still multiple possibilities, select the first one errors if a conversion or validation task fails, an error code is displayed a negative number indicates a ryze error a positive number indicates a p21e error was encountered in p21e, validations that are sent from ryze appear in the validation log the following errors may be displayed by ryze 255 "validation failed with an unexpected error" 101 "validation failed failed to prepare the shared file locations" 102 "validation failed the company is missing the p21e configuration" 103 "validation failed the asset group is missing the data package entry" 104 "validation failed no dataset data was found to validate" 105 "validation failed the asset group type is invalid" 106 "validation failed no valid external standard defined" 107 "data package url has an incorrect format" troubleshooting dataset conversions dataset conversions work with the dataset mapper plugin, see also docid\ e8oe3r3hx5oi7nr7snudr