Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Reference 360 SaaS
  • All Products

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

Back Next

Enable auto-generation of Code field values for a code list (v1)

Enable auto-generation of Code field values for a code list (v1)

Enables auto-generation of Code field values when you import code values to a code list that's created prior to the April 2025 release, if the Code field is configured with a rule association.

POST request

To enable auto-generation of Code field values when you import code values to a code list with a rule association configured for the Code field, submit a POST request with the following URI: 
/rdm-service/external/v1/codelists/<code list ID>/spkey/population/migrate

POST response

The response is in the JSON format.
The following table describes the attributes in the response:
Field
Type
Description
status
String
Status of the request.
The request can return one of the following statuses:
  • MIGRATION_SUCCESSFUL. Indicates that the request is successful.
  • MIGRATION_NOT_POSSIBLE. Indicates that the code list contains Code field values that don't match their source primary keys. For more information, contact Informatica Global Customer Support.
  • ALREADY_MIGRATED. Indicates that the request is successful and the code list is already enabled with auto-generation of Code field values.
  • NOT_APPLICABLE. Indicates that the Code field of the code list doesn't contain a rule association.
spKeyPopulationStatus.before
String
Status of the code list before running the request.
The code list can have one of the following statuses:
  • NOT_AVAILABLE. Indicates that the Code field of the code list doesn't contain a rule association.
  • UNKNOWN. Indicates that the request failed because of internal errors. For more information, contact Informatica Global Customer Support.
  • NOT_READY_FOR_MIGRATION. Indicates that the Code field of the code list contains a rule association but can't be enabled for auto-generation of Code field values because the code list contains Code field values that don't match their source primary keys. For more information, contact Informatica Global Customer Support.
  • READY_FOR_MIGRATION. Indicates that the code list is eligible for auto-generation of Code field values when you import code values to the code list.
  • MIGRATED. Indicates that the code list is already enabled for auto-generation of Code field values.
spKeyPopulationStatus.after
String
Status of the code list after running the request.
The code list can have one of the following statuses:
  • NOT_AVAILABLE. Indicates that the Code field of the code list doesn't contain a rule association.
  • UNKNOWN. Indicates that the request failed because of internal errors. For more information, contact Informatica Global Customer Support.
  • NOT_READY_FOR_MIGRATION. Indicates that the Code field of the code list contains a rule association but can't be enabled for auto-generation of Code field values because the code list contains Code field values that don't match their source primary keys. For more information, contact Informatica Global Customer Support.
  • MIGRATED. Indicates that the code list is enabled for auto-generation of Code field values.
invalidCodes
Object
Displays the details of invalid source primary keys and Code field values only if the status of the request is
MIGRATION_NOT_POSSIBLE
.

POST example

To enable auto-generation of Code field values when you import code values to a code list with a rule association configured for the Code field, you might use the following request: 
POST https://use4-mdm.dm-us.informaticacloud.com/rdm-service/external/v1/codelists/34cea9471fe977f7decef5f5/spkey/population/migrate HTTP/1.1
Accept: application/json
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
The following sample response shows a successful request that enabled auto-generation of Code field values for a code list: 
{
   "status":"MIGRATION_SUCCESSFUL",
   "spKeyPopulationStatus":{
      "before":"READY_FOR_MIGRATION",
      "after":"MIGRATED"
   }
}
Back to Top
0 COMMENTS
Back Next
We’d like to hear from you!