Difference between revisions of "Inherited Codelists - Trouble Shooting"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
# Export the codelist from the source Registry (ticking the settings box RAW) | # Export the codelist from the source Registry (ticking the settings box RAW) | ||
# Upload the exported codelist into the Target Registry | # Upload the exported codelist into the Target Registry | ||
| + | |||
| + | |||
| + | == Using Rollback == | ||
| + | |||
| + | When the Rollback facility is used, either from the Codelist page, the Activity - SDMX Transaction page or the Activity - Structure Submissions page any inheritance as such is not maintained. Instead the codes which were inherited from another codelist will be included in the 'Rollbacked" version of the codelist codelist. | ||
Revision as of 06:25, 19 April 2023
Environment Synchronisation
When using the Pull facility to obtain a codelist which has inherited it's codes from another codelist, the Inheritance link will not be retained. This is a known issue and will be addressed in a future release.
As a work around you can either
- Restore the inheritance manually (easiest option if the codelist has none of its own codes),
- or follow these steps:
- Delete the codelist from the target Registry
- Export the codelist from the source Registry (ticking the settings box RAW)
- Upload the exported codelist into the Target Registry
Using Rollback
When the Rollback facility is used, either from the Codelist page, the Activity - SDMX Transaction page or the Activity - Structure Submissions page any inheritance as such is not maintained. Instead the codes which were inherited from another codelist will be included in the 'Rollbacked" version of the codelist codelist.
