 |
Page History
...
| Duplicates in File | Duplicate rows within the imported file are not caught on Import. Improve in Sprint 37 - 2151. |
|---|
Tips for CDE Match
| Run Transform | CDE Match transforms the Source input into one row per column and permissible value. The command to transform the Source input details is "opt"+"cmd"+"t". |
|---|---|
| See Instructions | Please see the CDE Match Instructions document attached to this page. |
Tips for DEC Imports
| Validating Lots of Rows | Sometimes, the system throws an error when attempting to validate more than 4 rows at a time. If that happens, try validating a few rows at a time. |
|---|
...
None at this time.
Tips for PV VM Imports
| Import into Existing VD | The PV VM import is designed to import an enumeration into an existing Value Domain. PV/VMs can be created using existing VMs, or you can specify a new VM either with or without concept codes. |
|---|---|
| Specified VM Definition | Optional Specified VM Definition is only used if the VM Type is "TEXT". The system will not throw an error but it won't be added to the VM. The Caption and column heading in the template will be changed in Sprint 37 - 2131. |
| Possible Timeout | Validate/Create will timeout if more than 5 minutes. Try batches of 100 until we can redesign the code. Watch. |
| VM Reuse | In Sprint 36, if a Text VM is specified and an existing VM with the exact name is found, it will be reused, even if it has concepts. The Validation message will indicate that existing VM is being used (need to fix spacing). Is this ok? |
Tips for VM Match
| Column Order | VM Match is designed to find matching concepts and insert the Concept Name and Code into the grid. You can use Delivery Options to export the results and cut and past the contents of thse columns into the PV/VM Import to simplify creating the list of PV/VMs to import into a Value Domain. |
|---|
Tips for Designation Imports
...
