Difference between revisions of "Inherited Codelists - Trouble Shooting"
Jump to navigation
Jump to search
(Created page with "Category:How_To Category:How_To V11 == Environment Synchronisation == When using the Pull facility to obtain a codelist has inherited its codes from another codelist...") |
(→Environment Synchronisation) |
||
| Line 4: | Line 4: | ||
== Environment Synchronisation == | == Environment Synchronisation == | ||
| − | When using the Pull facility to obtain a codelist has inherited its 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 | + | When using the Pull facility to obtain a codelist has inherited its 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, 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 | ||
Revision as of 05:07, 19 April 2023
Environment Synchronisation
When using the Pull facility to obtain a codelist has inherited its 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, 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
