Reference 360

Back Next

Export value mappings to a CSV file

Exports the value mappings in a crosswalk to a CSV file.

POST request

To export value mappings in a crosswalk, submit a POST request with the following URI:

/rdm-service/external/v2/export

In the request header, you must specify the

attribute to

application/octet-stream

Use the following parameters in the request body to specify the crosswalk to export:

Field	Type	Description
delimiter	String	Delimiter used to separate values. Value must be ASTERISK , CIRCUMFLEX , COLON , COMMA , PIPE , SECTION , SEMICOLON , SPACE , or TAB .
codepage	String	Code page used for the export file. Value must be UTF8 .
decimalSeparator	String	Decimal separator used for numbers. Value must be COMMA or DOT .
thousandSeparator	String	Grouping separator used for numbers. Value must be COMMA , DOT , SPACE , SINGLEQUOTE , or NONE .
dateFormat	String	Format used for dates. Use one of the following formats: DE . For dd.mm.yyyy format. ISO . For yyyy-mm-dd format. US . For mm/dd/yyyy format.
filename	String	File name for the exported file. Value must end with the .csv file extension.
containerType	String	Type of asset that contains value mappings. Value must be crosswalk .
containerId	String	The ID of the crosswalk. You can find the ID of assets in Reference 360 or use REST APIs to retrieve the IDs. For more information, see Asset IDs.

POST response

The response is a CSV file. The CSV file contains two header rows followed by data rows.

The CSV file uses the following columns:

status.key

and

effectiveDate

. Based on your data model, you might have additional columns in the file.

POST example

To export the value mappings in a crosswalk, you might use the following request:

POST https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v2/export HTTP/1.1
Content-Type: application/json
Accept: application/octet-stream
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX

{
  "delimiter" : "SEMICOLON",
  "codepage" : "UTF8",
  "decimalSeparator" : "COMMA",
  "thousandSeparator" : "DOT",
  "dateFormat" : "ISO",
  "filename" : "testdata.csv",
  "containerType" : "crosswalk",
  "containerId" : "5d123f6e4077c700010d59e4"
}

The following sample response shows the exported data in a CSV file:

HTTP/1.1 200 OK
Content-Disposition: attachment;filename=testdata.csv
Content-Type: application/octet-stream
Content-Length: 578

sourcePKey,_from.id.sourcePKey,_to.id.sourcePKey
sourcePKey,_from.id.sourcePKey,_to.id.sourcePKey
sourceCode0_targetCode0,sourceCode0,targetCode0
sourceCode1_targetCode1,sourceCode1,targetCode1
sourceCode2_targetCode2,sourceCode2,targetCode2
sourceCode3_targetCode3,sourceCode3,targetCode3
sourceCode4_targetCode4,sourceCode4,targetCode4
sourceCode5_targetCode5,sourceCode5,targetCode5
sourceCode6_targetCode6,sourceCode6,targetCode6
sourceCode7_targetCode7,sourceCode7,targetCode7
sourceCode8_targetCode8,sourceCode8,targetCode8
sourceCode9_targetCode9,sourceCode9,targetCode9

Rename Saved Search

Table of Contents

Reference 360

Reference 360

Export value mappings to a CSV file

Export value mappings to a CSV file

POST request

POST response

POST example