Table of Contents

Search

  1. Preface
  2. Introducing Reference 360
  3. Getting started with Reference 360
  4. Manage system reference data
  5. Manage reference data sets
  6. Manage code lists
  7. Manage code values
  8. Manage crosswalks
  9. Import data
  10. Manage hierarchies
  11. Manage attributes
  12. Manage workflows
  13. Manage jobs
  14. Reference 360 REST API
  15. Glossary

Reference 360

Reference 360

Exporting code values

Exporting code values

Export code values in a code list.
Before you begin, you must get a session ID and identify the asset ID. The session ID authenticates your requests. The asset ID is the ID of the code list that contains the code values that you want to export. For more information, see Session IDs and Asset IDs.
  1. To export code values in a code list, use the Export code values REST API.
    For more information about the Export code values REST API, see
    Export code values to a CSV file
    .
    For example, the following request exports code values:
    POST https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v1/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" : "codelist", "containerId" : "1989aae96bdaa4c2b8768fcc" }
    The
    containerId
    attribute is the ID of the code list that contains the code values that you want to export.
    For example, the following response contains the exported code values:
    HTTP/1.1 200 OK Content-Disposition: attachment;filename=testdata.csv Content-Type: application/octet-stream Content-Length: 124 status.key;effectiveDate;approvedOn status.status.key;effectiveDate;approvedOn ActiveStatus;myEffectiveDate;myApprovedOn ActiveStatus;myEffectiveDate;myApprovedOn

0 COMMENTS

We’d like to hear from you!
Arindam Ghosh - December 20, 2024

To which folder/path does it export the csv file? Can we customize that and choose our own secure agent directory path?

Informatica Documentation Team - December 20, 2024

Hi Arindam,

We’re working to address your comments and will get back to you.

Thanks,

Informatica Documentation team


Arindam Ghosh - January 15, 2025

Is there any update on this please?

Informatica Documentation Team - January 16, 2025

Hi Arindam,

The data is not directly exported to any CSV file. The API response contains the exported code values. You can use your REST API client to save the response with the exported code values to a CSV file.

We've also updated the lead-in sentence of the sample response in the documentation for clarity.

Thanks,

Informatica Documentation team


Arindam Ghosh - January 16, 2025

Understood, then why we are passing the key value pair ("filename" : "testdata.csv") in the JSON payload if we have to save the file manually ?

Informatica Documentation Team - January 17, 2025

Hi Arindam,

The "filename":"testdata.csv" parameter in the request is a mandatory parameter that maps to the Content-Disposition header in the response, and it specifies whether the content can be displayed in a browser or saved as an attachment. In this case, when you save the response to a file locally, it gets saved with the file name as testdata.csv.

We'll update the description for the "filename" parameter in the documentation and update the comment thread as soon as the updates are published.

Thanks,

Informatica Documentation team


Informatica Documentation Team - February 04, 2025

Hi Arindam,

We’re happy to let you know that we addressed your feedback in the documentation.

You can find the updated description for the filename parameter in Export code values to a csv file.

Thanks,

Informatica Documentation team