Inherited Codelists - Trouble Shooting
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 (Revisions), 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.
If this behaviour is not acceptable, prior to performing rollback, export any inherited codelists as detailed for Environment Synchronisation above. This will restore the inheritance link.
Re-assigning structures to a different Agency
When using the Delete and Reassign Agency feature the Inheritance link will not be retained. This is a known issue and will be addressed in a future release.
To rectify this, you will need to manually recreate the the inheritance. To assist with this process you can follow these steps:
- Take a copy of any codes that exist in the codelist which has the inheritance link prior to using Re-assign by editing the codelist and copying the contents of the "Show CSV" option in step 4 of the wizard.
- In the codelist which needs re-instating, add the linked codelist in step 1 of the codelist wizard
- In step 4 or the wizard, go to show CSV and remove all the codes shown
- Paste the copy you too prior to Re-assign (see step X above) back in and then update and save the codelist.
