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

Dependent reference data sets

Dependent reference data sets

A dependent reference data set depends on another reference data set and passes down its dependency to its code lists.
When you configure a reference data set as dependent, the reference data set that it depends on is referred to as the parent dependency. Reference data sets can have only one parent dependency. When you create code lists in a dependent reference data set, the code lists inherit the same parent dependency.
After you create a dependent reference data set, you cannot change the structure definition. If you create a code list in a dependent reference data set, the code list must use the inherited structure definition.
For example, you have a Country Codes reference data set. When you create a State Codes reference data set, you define the structure definition as dependent and configure the Country Codes reference data set as the parent dependency. Then when you create code lists in the State Codes reference data set, the code lists inherit the dependency on the Country Codes reference data set. For each code list in the State Codes reference data set, you can choose the code list dependency. A code list dependency defines the dependent relationship between one code list and another. You might want the Enterprise State Codes code list to depend on the Enterprise Country Codes code list.
The State Codes reference data set depends on the Country Codes reference data set and the code values within this set.

0 COMMENTS

We’d like to hear from you!