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

Get failed import job report

Get failed import job report

Retrieves an error report for a failed import job.
By default, the error report shows the first 100,000 records. To retrieve more records or to view the next page of records in the error report, use the query parameters.

GET request

To retrieve an error report for a failed import job, submit a GET request with the following URI:
/rdm-service/external/v1/import/job/<job Id>/errorDetails
To retrieve the paginated error report, submit a GET request with the following query parameters appended to the URI:
/rdm-service/external/v1/import/job/<job Id>/errorDetails?pageNum=<page number>&recordsPerPage=<records per page>

GET request query parameters

You can append the query parameters to the URI to retrieve paginated errors.
The following table lists the query parameters:
Parameter
Description
pageNum
Optional. Page number to display. Default value is
0
.
recordsPerPage
Optional. Number of records to display per page. Default value is
100000
.

GET response

The response contains the error details, such as the line where the error occurred and the reason.
The following table describes the attributes in the response:
Field
Type
Description
jobId
String
ID of the job.
entityType
String
Type of entity imported. Value is
BusinessEntity
or
Relationship
.
fileName
String
Name of the file. Value must end with the
.csv
file extension.
entityName
String
Name of the entity.
errorDetails
-
Includes the error details.
lineNumber
Number
Line number where the error occurred.
entitySourcePkey
String
Column identifier.
reasons
Array
Explanation of failure.

GET example

To retrieve an error report for a failed import job, you might use the following request:
GET https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v1/import/job/dae4301e9369c16c08bf0881/errorDetails HTTP/1.1
To retrieve the second page of records in a paginated error report with 100 records per page, you might use the following request:
GET https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v1/import/job/dae4301e9369c16c08bf0881/errorDetails?pageNum=2&recordsPerPage=100 HTTP/1.1
The following sample response shows the error report for a failed code values import job:
HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Content-Length: 395 IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX { "jobId":"5984980d317a4b00cfe18880", "entityType":"BusinessEntity", "fileName":"import.csv", "entityName":"rdm.value.be.442ac56e11d5fc9bb11f6a3f", "errorDetails":[ { "lineNumber":1, "entitySourcePkey":"Code-1101", "reasons":[ "The code value INX does not exist in the picklist that is in the path Country. Specify a code value from the picklist." ] } ] }
The following sample response shows the error report for a failed value mappings import job:
HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Content-Length: 354 { "jobId":"dae4301e9369c16c08bf0881", "entityType":"Relationship", "fileName":"import.csv", "entityName":"rdm.crosswalk.rel.21ffd6b5f92d10c744acc27c.fc66c441288cf898c6fe5023", "errorDetails":[ { "lineNumber":1, "entitySourcePkey":"AF_AFG", "reasons":[ "The requested resource with ID 'AFG' does not exist." ] } ] }

Back to Top

0 COMMENTS

We’d like to hear from you!