Difference between revisions of "Inherited Codelists - Trouble Shooting"

From FMR Knowledge Base
Jump to navigation Jump to search
(Environment Synchronisation)
Line 7: Line 7:
 
As a work around you can either
 
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:
+
* 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
 
# Delete the codelist from the target Registry
 
# 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

Revision as of 06:09, 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:
  1. Delete the codelist from the target Registry
  2. Export the codelist from the source Registry (ticking the settings box RAW)
  3. Upload the exported codelist into the Target Registry